Meeting 11-29-04 Attendance Jim Lewis Dave Bishop Charlie Guy John Ries Peter Ashenden Chuck Swart Code Review FT 5 to_string with real and digits just calls to_string with format using "0.F" as the format string. Updated to_string for real and time to match previous discussions. FT8 TEE function modified to used OUTPUT, as per action item. Peter discussion on have implicit to_string function for each type. Has one arguement with value. There is a problem with implicit to string that when we define the first type in standard we need to have STRING defined but we need to have character defined first So this is a problem. Could be solved with "magic". Could be used for defered type definitions if extended to types other than access type. Possible solution is to extend 'image. Has problem with verboseness. FT5a action item for Peter to write up implicit proposal FT8 How do we close if we need code review? Need to farm out the reviews with an owner. Floating Point Packages using generics Issue with round_type needs to be visible for conversion between different real types. Along with valid_fp_state. Issue if put in the generic package rather than the base package. Proposal is to change fphdl_base_pkg to fphdl_base_types and other functions moved into the fphdl_pkg body and be private to the type. Jim has issue that the type info is be outside of IEEE. We could specify instance in the IEEE library Discussion on just have the package parameterized on fp_round_style, fp_denormalized, fp_check_error, fp_guard_bit. Subtypes are used to control the width. The package would define 16/32/64/128 bit subtypes. Peter package we have appears to be full Jim's issues: Number of package instantations. Instantations are in user's library and not ieee library. Peter should we take this off line and look at use models and see what is correct. FT18 Proposal needs to updated action item Peter FT16 (context) Note we have a new keyword. Will have some updates. Why only have one context references? Primary and secondary already allow using 2 context references. General feeling is that multiple context references would be okay. Example needs a "Library project_lib" and the IEEE clause needs library IEEE. Peter to update to allow for multiple context clauses. Action items Peter A. write up implicit to_string function for all types for FT5a. Jim and David for usage model of floating point package. Peter A. action item update FT18 to reflect e-mail discussion results. Peter A to update FT16 to reflect multipl context clause and correct examples. Next meeting Dec 20th.