RE: [sv-ac] updated proposal for 1641

Hi Manisha,

 

I have re-reviewed the proposal relative to d4. I did not find anything
specific to d4, but I did notice the following 1361 related issue that
is easy to fix in this proposal:

 

In 16.3, it states,

 

If an assertion fails and no else clause is specified, the tool shall,
by default, call $error, unless a toolspecific

option, such as a command-line option, is enabled to suppress the
failure.

 

If an assertion fails and no else clause is specified, the tool shall,
by default, call $error, unless a toolspecific

option, such as a command-line option, is enabled $assertfailoff is used
to suppress the failure.

 

I don't think we need to mention what tool specific options can do.
Similarly, in the new text added to 19.9, I don't think we need to say: 

 

"The display of messages of warning and information types can be
controlled by a tool-specific option, such as a command-line option."

 

At some point, there could exist system tasks for this also.

 

________________________________

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Kulshrestha, Manisha
Sent: Friday, October 05, 2007 3:28 AM
To: sv-ac@eda-stds.org
Subject: [sv-ac] updated proposal for 1641

 

Hi,

 

I have uploaded updated proposal for 1641. The latest proposal is
severity_tasks_7.pdf. The changes were made based on the feedback in the
mantis. The feedback was to not repeat the same information in chapter
16 as the details about the tasks were in clause 19.9. Please review the
changes and let me know your feedback.

 

Could someone forward this to sv-bc .

 

Thanks.

Manisha 


-- 
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.