[sv-ac] RE: Call to vote: Due May 16

Hello Dmitry,

here is my vote:

Mantis 3213 __X__ Yes __X__ No

http://www.eda-stds.org/mantis/view.php?id=3213
http://www.eda-stds.org/mantis/file_download.php?file_id=5003&type=bug

In 16.5.1, first item: If a variable is declared in a task, that variable is sampled as any other variable, independent of calls to the task.
You mean task calls in match items? What about variables declared in functions called in Boolean expressions? Should this line have a little more explanation?

In For example, if a is a variable, then the value of const'(a) in the concurrent context is the current value of a.
Should it say concurrent assertion context, since concurrent context is not defined?

I do not quite understand (in red)
The change (or lack of change) is determined by comparing the sampled value of the expression with the sampled value of the expression evaluated in the Postponed region of the most recent strictly prior time step in which the clocking event occurred.
Sampled value was defined as the value taken in the preponed region. Is this changing the definition for this particular case here? If not, then why to mention it since the sampled value is stable throughout the time step. If it changes the definition, then the sampled value in postponed region would reflect the changed value as a consequence of the clock tick. So, if the clock tick occurred just in the preceding time step, the current sampled value and the one from the preceding postponed region are the same. No change detected?

Similarly in
The other functions are defined as follows (the comparison is done between the sampled value at the invocation point and the sampled value in the Postponed region of the next tick of the global clock):

Mantis 3385 __X__ Yes ____ No

http://www.eda-stds.org/mantis/view.php?id=3385
http://www.eda-stds.org/mantis/file_download.php?file_id=4999&type=bug

Best regards,
ed

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.