Peter, -- pragma Jim's biased opinion on ... Since the other base packages are including textio read and write routines and since textio cannot be moved into package standard, it would seem a good compromise would be to implicitly reference it. Of course, one reason not to include textio would be based on a belief that using some enhancement to the language we can come up with a better set of functionality that will replace textio totally. Do you have something in mind? I realize that perhaps we are referencing a package that is not used (such as with RTL designs), but is there a penalty in terms of simulation performance for referencing a package that is not used? On the other hand, just referencing library IEEE w/o the other packages, does not do alot and perhaps would be better to be included in a context clause. Cheers, Jim > Folks, > > FT29 proposes to include the following in the standard context: > > use std.textio.all ; > library ieee ; > > That is, each design unit should implicitly include these clauses in its > context clause. > > Now that we have a complete proposal for context declarations (FT16), may I > suggest that it largely obviates FT29? In that case, we can drop FT29 from > consideration. > > Comments? > > Cheers, > > PA > > -- > Dr. Peter J. Ashenden peter@ashenden.com.au > Ashenden Designs Pty. Ltd. www.ashenden.com.au > PO Box 640 Ph: +61 8 8339 7532 > Stirling, SA 5152 Fax: +61 8 8339 2616 > Australia Mobile: +61 414 70 9106 > > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jim Lewis Director of Training mailto:Jim@SynthWorks.com SynthWorks Design Inc. http://www.SynthWorks.com 1-503-590-4787 Expert VHDL Training for Hardware Design and Verification ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Received on Tue Mar 29 07:24:57 2005
This archive was generated by hypermail 2.1.8 : Tue Mar 29 2005 - 07:25:16 PST