[sv-ac] AC 196:

From: Eduard Cerny <Eduard.Cerny@synopsys.com>
Date: Fri Nov 12 2004 - 13:37:37 PST

Hello Hillel,

- the proposal should make the type spec optional.

- if specified, it should be from only the existing types that are allowed
for expressions in concurrent assertions.

- if passed by value, e.g., int x, what is the value? Is the one at the
first clock tick of every eval. attempt, the value at time 0, other?

- if passed by reference, e.g., ref int x, I would suppose that if used in
expressions it will be the value sampled at each clock tick or the immediate
value if used in disable iff? It can be read and written.

- if specified as const ref, it should only allow reading.

- if passed by ref, is it possible to assign the variable in the sequence
even if it is not a local variable of a sequence / property? E.g., an
external variable to the assertions (I would like that...)

- if the type is optional, then it seems that the changed BNF would have
tf_port_list instead of list_of_formals. I suppose the type is optional
because in the "implicit" form the "packed_dimension" is optional {}.
Correct?

Best regards,
ed
Received on Fri Nov 12 13:37:03 2004

This archive was generated by hypermail 2.1.8 : Fri Nov 12 2004 - 13:37:19 PST