David,
Integers as defined by the language are at a minimum
32 bit signed numbers. There should not be any more
ambiguity here that is not already part of READ for
integer.
> Looking at these funcitons in FT-08
>
> procedure HREAD (L: inout LINE; VALUE: out INTEGER; GOOD : out
> BOOLEAN);
> procedure HREAD (L: inout LINE; VALUE: out INTEGER);
> procedure OREAD (L: inout LINE; VALUE: out INTEGER; GOOD : out
> BOOLEAN);
> procedure OREAD (L: inout LINE; VALUE: out INTEGER);
> procedure BREAD (L: inout LINE; VALUE: out INTEGER; GOOD : out
> BOOLEAN);
> procedure BREAD (L: inout LINE; VALUE: out INTEGER);
>
> The big question here is "do I have a signed or unsigned number?"
> This was the main reason behing the "numeric_std" function.
>
> I would rather make people use "numeric_std" than force an ambiguity that
> we tried so hard to prevent.
Some people like to use integers due to their superior
simulation performance.
Cheers,
Jim
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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 Fri Jun 25 14:03:18 2004
This archive was generated by hypermail 2.1.8 : Fri Jun 25 2004 - 14:03:19 PDT