[sv-ac] RE: Reviewing 3191 (triggered method on sequence formals)

By the way, the reason that this problem comes up only (or at least mainly) in the assertions part of the language, is that SVA is the only part of the language that uses substitution semantics, different from the rest of the language.

Shalom

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Seligman, Erik
Sent: Thursday, March 10, 2011 8:07 PM
To: sv-ac@eda-stds.org
Subject: [sv-ac] Reviewing 3191 (triggered method on sequence formals)

Hi guys-I carried out my action item to take a look at this proposal. Can someone remind me why we wanted to do an extension specific to sequence formal arguments, instead of defining the triggered method for general sequences? In particular, this paragraph seems very awkward to me:

There is one case in which the rewriting algorithm produces a legal flattened sequence which would not be legal in the source text: when an actual argument is a sequence expression and it is substituted for a reference to the corresponding formal argument standing as the operand of a sequence method call. In this case, the substitution produces a sequence expression, enclosed in parentheses, as the operand of the sequence method call. This is illegal in the source text, but is allowed as a result of the rewriting algorithm. All other cases in which the flattened sequence is illegal shall result with an error.

Do we really want to make this such a special case? Would it really be easier to define/implement this extension rather than just making the method defined for any sequence expression?

Defining triggered method for sequence arguments
Can we allow a sequence method on formal arguments

i.e.
property p (sequence s);
       s.triggered;
endproperty

Mantis 3191
Jacob: It's not legal to call triggered method on sequence s. (because of
       substitution semantics?). Could we do a smaller extention to allow
       only this case?
       A more comprehensive proposal would be to allow calling the triggered
       method on any sequence expression.

3191: Anupam and Erik will review this proposal

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
---------------------------------------------------------------------
Intel Israel (74) Limited
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.