RE: [sv-ac] Mantis 1641

I opened a new Mantis 2335.

Thanks,
Dmitry

-----Original Message-----
From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On
Behalf Of Neil Korpusik
Sent: Wednesday, March 19, 2008 11:19 PM
To: Kulshrestha, Manisha
Cc: Bresticker, Shalom; sv-ac@server.eda.org
Subject: Re: [sv-ac] Mantis 1641

Mantis item 1641 has already been approved by the Champions
and the Working Group. If you attempt to make any changes to
it you run the risk of having the whole proposal getting hung up.

My suggestion is to open a new Mantis item for the minor change
that Shalom has flagged. If the sv-ac wants to address this issue
the committee chair should make a request to me, so that I can
bring it up in the Working Group meeting next Thursday.


Neil





Kulshrestha, Manisha wrote:
> Hi Shalom,
> 
>  
> 
> I'll check this and get back to you tomorrow.
> 
>  
> 
> Thanks.
> 
> Manisha
> 
>  
> 
> *From:* owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org]

> *On Behalf Of *Bresticker, Shalom
> *Sent:* Sunday, March 16, 2008 7:22 PM
> *To:* sv-ac@server.eda.org
> *Subject:* [sv-ac] Mantis 1641
> 
>  
> 
> Hi,
> 
> Mantis 1641 contains the following text for 16.3:
> 
> The information about assertion failure can be printed using one of
the 
> following severity system tasks in the action block.
> 
> - $fatal is a run-time fatal.
> - $error is a run-time error.
> - $warning is a run-time warning.
> - $info indicates that the assertion failure carries no specific
severity.
> 
> The problem is that the current LRM has for $warning:
> - $warning is a run-time warning, which can be suppressed in a 
> tool-specific manner.
> 
> In the proposal, the second half of the sentence disappeared, without 
> being explicitly deleted. The proposal does explicitly delete the 
> parallel text in 19.9.
> 
> The proposal also replaces the following text in 16.3:
> 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.
> 
> with this:
> If an assertion fails and no* **else* clause is specified, the tool 
> shall, by default, call $error, unless $assertfailoff is used to 
> suppress the failure.
> 
> I think the proposal should explicitly delete the phrase ", which can
be 
> suppressed in a tool-specific manner" in 16.3.
> 
> Thanks,
> Shalom
> 
> Shalom Bresticker
> Intel Jerusalem LAD DA
> +972 2 589-6582
> +972 54 721-1033
> 
> ---------------------------------------------------------------------
> 
> 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* <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.


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