Hi Hillel;
Here is my feedback.
1. Provide types on formal parameters
Yes.
2. <implies multiple features/proposals/items> - can not provide an answer.
4. Support pass-by-value
5. Support pass-by-reference
6. Support pass-by-reference with 'ref' keyword.
NO - these are terms used in Software languages.
Software == task call
Hardware == instance, ports
Assertions are based on a Hardware mindset - wires (nets.)
7. Handle sequence and property type arguments as untyped arguments.
Would prefer types, but nothing has been discussed for specifying a type
for sequences, or for specifying a type that can allow a signal/expression
or a sequence.
Thanks.
Adam Krolnik
Verification Mgr.
LSI Logic Corp.
Plano TX. 75074
Co-author "Assertion-Based Design"
Received on Fri Nov 19 12:57:37 2004
This archive was generated by hypermail 2.1.8 : Fri Nov 19 2004 - 12:57:58 PST