Hi Ed,
Thank you for your comments. I uploaded the updated version:
Word: http://www.eda-stds.org/mantis/file_download.php?file_id=4934&type=bug
PDF: http://www.eda-stds.org/mantis/file_download.php?file_id=4935&type=bug
I am also attaching the document with my answers to your comments. Note that this is not the final version and it does not contain the fixes, but only my answers to your comments. See my also my comments below.
Thanks,
Dmitry
From: Eduard Cerny [mailto:Eduard.Cerny@synopsys.com]
Sent: Monday, April 18, 2011 22:49
To: Korchemny, Dmitry
Cc: 'sv-ac@eda-stds.org'; Eduard Cerny
Subject: 3213 - comments
Hello Dmitry,
please find attached the docx file of 3213 with my comments and small changes inserted. (Change tracking on.)
I accepted the change from $sampled to $concurrent, but would it not be simpler to use $sampled and define its meaning as you did for $concurrent?
[Korchemny, Dmitry] This was my initial intent but there was a strong opposition from Tom and Gord, since sampled has a well-defined meaning - the value in the Preponed region. Therefore I introduce a new concept instead of extend (abuse?) the existing one.
On the other hand, if $concurrent is introduced, it might be useful to have $sampled in the case the user really want the value from the end of the preceding time step in the cases where $concurrent would return the current value?
[Korchemny, Dmitry] I could not think about any case where it could be useful. From all cases where $concurrent returns the current value, $sampled would be meaningful only for free checker variables, but it looks to be a bad practice to do so instead of using $past_gclk. Do you have some specific use case in mind?
best regards,
ed
---------------------------------------------------------------------
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.
This archive was generated by hypermail 2.1.8 : Wed Apr 20 2011 - 06:18:32 PDT