RE: [sv-bc] release/deassign with variables driven by continuous assignments

But 6.5 says explicitly (and this is in 1800-2005 as well):

"For the purposes of the preceding rule, a declared variable
initialization or a procedural continuous assignment is considered a
procedural assignment. A force statement is neither a continuous nor a
procedural assignment. A release statement shall not change the variable
until there is another procedural assignment or shall schedule a
reevaluation of the continuous assignment driving it. A single force or
release statement shall not be applied to a whole or part of a variable
that is being assigned by a mixture of continuous and procedural
assignments."

Shalom


> -----Original Message-----
> From: owner-sv-bc@server.eda.org 
> [mailto:owner-sv-bc@server.eda.org] On Behalf Of Steven Sharp
> Sent: Thursday, October 11, 2007 8:32 PM
> To: Dave_Rich@mentor.com; sv-bc@server.eda.org; Bresticker, Shalom
> Subject: RE: [sv-bc] release/deassign with variables driven 
> by continuous assignments
> 
> 
> >From: "Bresticker, Shalom" <shalom.bresticker@intel.com>
> 
> >Actually, is it legal to do a procedural continuous assignment to a 
> >variable driven by a continuous assignment? I thought not. 
> And if not, 
> >then that entire part of the text in 10.6.1 should be deleted.
> 
> I believe that procedural continuous assignments were 
> deliberately not classified as procedural assignments, 
> probably so that forces (which are a type of procedural 
> continuous assignment) could be used on them.
> 
> Steven Sharp
> sharp@cadence.com
> 
> 
> --
> 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.