One of the proposals at the bottom of our proposals page is:
http://www.eda-twiki.org/vhdl-200x/vhdl-200x-ft/proposals/dta_type_genericity.pdf
Which describes how to add generics to packages.
In NUMERIC_STD there is a constant called "NO_WARNING".
This constant turned out to be very useful to us while debugging
the packages. It is also useful to the users, but there is
no way for them to get at it.
Some vendors have even implemented special options to turn this
"no_warning" boolean on.
Now, why can't we do the following:
packages numeric_std is
generic (no_warning : boolean := false);
Then the user could say:
use ieee.numeric_std.all;
architecture rtl of whatever
package numeric_std_nowarn is new numeric_std
generic map (no_warning => true);
...
begin
and warnings would be shut off. (If I read this proposal
correctly)
This also helps out with the fixed and floating point packages
to control rounding and overflow.
Shall I or Shall I not? I know I'm sending out lots of e-mails,
but I will not make a major change to the packages without checking
first.
-- David W. Bishop dbishop@vhdl.org All standard disclaimers apply.Received on Thu Aug 26 13:06:10 2004
This archive was generated by hypermail 2.1.8 : Thu Aug 26 2004 - 13:08:33 PDT