Hi Lisa, I agree with Bassam. I am also citing below my previous mail: Thanks, Dmitry $past( expression1 [, [number_of_ticks] [, [ expression2] [, [clocking_event]]]] ) . because it makes writing scripts easier: there is no need to analyze whether the clocking event has been provided or not; the invocation string will remain exactly the same. Here is a small Perl example: sub writePastOfSig { my $clockEvent = shift; print "\$past(sig, 1, 1, $clockEvent)"; } Both invocations writePastOfSig("@(posedge clk)"); and writePastOfSig(); will work correctly with this definition. With the first alternative the code of writePastOfSig should be more complex. The second alternative is also consistent with the syntax of the general function invocation: list_of_arguments ::= [ expression ] { , [ expression ] } { , . identifier ( [ expression ] ) } | . identifier ( [ expression ] ) { , . identifier ( [ expression ] ) } If so, the definition of other sampled value functions should be rewritten accordingly. ________________________________ From: Bassam Tabbara [mailto:Bassam.Tabbara@synopsys.com] Sent: Wednesday, January 24, 2007 10:46 PM To: Lisa Piper; Korchemny, Dmitry; sv-ac@eda-stds.org Subject: RE: [sv-ac] 1591is ready for review Hi Lisa, It is the norm I believe e.g. see p. 159 of LRM. Thx. -Bassam. ________________________________ From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Lisa Piper Sent: Wednesday, January 24, 2007 12:36 PM To: Korchemny, Dmitry; sv-ac@eda-stds.org Subject: RE: [sv-ac] 1591is ready for review Hi Dmitry, I did not see any errors but have one question - why do you prefer to allow the extraneous comma at the end: e.g. $past ( var , ) Lisa ________________________________ From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Korchemny, Dmitry Sent: Wednesday, January 24, 2007 10:49 AM To: sv-ac@eda-stds.org Subject: [sv-ac] 1591is ready for review Hi all, I have uploaded the proposed solution. Please, review. Thanks, Dmitry -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Jan 25 00:06:37 2007
This archive was generated by hypermail 2.1.8 : Thu Jan 25 2007 - 00:07:04 PST