[sv-ac] RE: Draft 3 Review

Hi Dmitry,

For - Mantis 2412

Sec 16.14.3 (page 401, line 36) - this paragraph should be as below (we decided that we need to make this change in the editing phase).
Similarly, the scope of a clocking event flows into an instance of a named property or sequence, regardless of whether method triggered or method matched is applied to the instance of the sequence. The scope of a clocking event flows into an instance of a named sequence provided neither method triggered nor method matched is applied to the instance of the sequence. The scope of a clocking event flows left to right across an instance of a property or a sequence, regardless of whether method triggered or method matched is applied. A clocking event in the declaration of a sequence or property does not flow out of an instance of that sequence or property.

Sec 16.14.6 (page 406, line number 46-47) - indentation is missing before $display - should look like
always @(s_f)
    $display("sequence triggered");

Anupam

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Korchemny, Dmitry
Sent: Tuesday, November 08, 2011 11:31 PM
To: sv-ac@eda-stds.org
Subject: [sv-ac] Draft 3 Review

Hi all,

Draft 3 is ready for review. You are requested to review Draft 3 sections and the implemented Mantis items as listed below. Please, confirm.

Name

Mantis

Sections

Eduard Cerny

3766

14, 17 - 17.3

Ben Cohen

2578

A

Dana Fisman

3135

F

Tapan Kapoor

37, 39

Jacob Katz

3191

16-16.8

Dmitry Korchemny

3722, 2556

16.13.15 - 16.15.5

Scott Little

2732

22, Annex B, C, P

Manisha Kulshrestha

20

Anupam Prabhakar

2412

16.9

Erik Seligman

3385

17.4 - End

Samik Sengupta

16.10 - 16.13.14

 Tom Thatcher

2722

16.15.6 - End

Thanks,
Dmitry
---------------------------------------------------------------------
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<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.