RE: [sv-ac] 1932and one more small font correction

All my amendments are fixed.

 

Lisa

 

________________________________

From: Bustan, Doron [mailto:doron.bustan@intel.com] 
Sent: Thursday, January 31, 2008 1:20 AM
To: Lisa Piper
Cc: Korchemny, Dmitry
Subject: RE: [sv-ac] 1932and one more small font correction

 

Fixed

 

Doron

 

________________________________

From: Lisa Piper [mailto:piper@cadence.com] 
Sent: Thursday, January 31, 2008 12:12 AM
To: Bustan, Doron
Cc: Korchemny, Dmitry
Subject: RE: [sv-ac] 1932and one more small font correction

 

Sorry!  More font issues. This was the last you sent before going to
sleep.

 

1. not's are not bold

 

not (sequence_expr |-> not property_expr)

and sequence_expr #=# property_expr is equivalent to the following:

not (sequence_expr |=> not property_expr)

 

2. until should be bold

 if-else, and the until operators) until it is replaced by a new
clocking event.

 

3. this was there previously - shouldn't if and else be bold?

- The set of semantic leading clocks of if (b) q1 else q2 is
{inherited}.

 

4. operators next, always, until, and eventually should be bold?

The rules for using multiclocked overlapping implication/followed-by,
and if/if-else, and the next,

always, until, and eventually operators in the presence of an incoming

outer clock can now be stated more precisely.

 

 

 

________________________________

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Bustan, Doron
Sent: Wednesday, January 30, 2008 3:58 PM
To: sv-ac@eda.org
Subject: [sv-ac] 1932and one more small font correction

 

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