RE: [sv-ac] #1510

Hi Manisha,

 

The user could write his property for side effects (actions associate
with sequences) and because of the success statement. This is usually
ugly, but specifying an explicitly void else statement indicates such an
intent.

 

Dmitry

 

________________________________

From: owner-sv-ac@server.eda-stds.org
[mailto:owner-sv-ac@server.eda-stds.org] On Behalf Of Kulshrestha,
Manisha
Sent: Monday, July 31, 2006 8:04 PM
To: Bassam Tabbara; sv-ac@server.eda-stds.org
Subject: RE: [sv-ac] #1510

 

Hi,

 

I think saying "do nothing" on property failure is same as not writing
the property. So, effectively, user is wasting his/her time by saying do
not report anything even if property fails. If the user really wants "do
nothing" behaviour he/she should remove the property instead of writing
null else clause. It is also error prone if use by mistake creates a
null statement for else clause and thinks that property passed (because
no failure was reported by the tool) whereas it actually did not.

 

Thanks.

Manisha

 

________________________________

From: Bassam Tabbara [mailto:Bassam.Tabbara@synopsys.com] 
Sent: Friday, July 28, 2006 7:59 PM
To: Kulshrestha, Manisha; sv-ac@eda-stds.org
Subject: RE: [sv-ac] #1510

Hi Manisha,

 

About your 2nd change in proposal, the null stmt form to me really means
"do nothing", so the $error call treatment as if no else was specified
bugs me.

 

Thx.

-Bassam.

 

 

________________________________

From: owner-sv-ac@eda-stds.org [mailto:owner-sv-ac@eda-stds.org] On
Behalf Of Kulshrestha, Manisha
Sent: Friday, July 28, 2006 3:41 PM
To: sv-ac@eda-stds.org
Subject: [sv-ac] #1510

Hi,

 

I have uploaded proposal for 1510. 

 

Thanks.

Manisha