Re: [vhdl-200x] Modular types, alternative solutions

 > Nothing is wrong with numeric_x.  The place where this crops up most
 > annoyingly for me is
 > passing tables into/out of VHDL via files (e.g. Matlab generated
 > memory table initialization, filter
 > coefficients, test vectors) and passing tables of constants into an
 > entity through a generic, which I
 > typically do with an array of integers (array of numeric_std is
 > awkward for large tables, and is
 > not supported for passing through generics by many vendors).

I'd like to understand why array of numeric_std is awkward for
large tables.  I think that decimal bit-string literals (when
available) should improve the situation.

 > While I agree the long integer
 > issue  is mostly a vendor issue, the fact that there is not an
 > explicit long integer type in the standard
 > makes longer than 32 bit integers risky due to sporadic and not
 > required support for them.

I see the point.  But I am not sure that having a standard 64 bit
situation would magically change the vendor implementation.  I still
think that user requests are a better way to change vendor
implementation.

 > I generally do use numeric_std for description of the logic, and
 > usually in my test benches.  You do
 > have to convert to/from integer to get access to the ieee.math_real
 > library in order to get to the
 > trig and other math functions for use in a testbench, and there the
 > 32 bits can become an issue as well.

I don't really understand here.  ieee.math_real is mostly about the
real type.  Why do you need to convert from/to integer ?  Is it
because you are using numeric_x for fixed point ?

Tristan.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.