RE: [sv-bc] FW: Mantis item filed re. force/release behavior description

Gran, all-
Thanks for your explanations- these are clear.  My issue was with the
original sentence that was not, i.e. one could infer from the wording
of that sentence that the simulator could arbitrarily choose to take
*either* action under some circumstances.

In any case, if the proposed solution for #2097 is approved, my #2152
entry is moot, since this sentence will be deleted in the next draft.
-Chuck

-----Original Message-----
From: Gran, Alex [mailto:alex_gran@mentor.com] 
Sent: Thursday, October 25, 2007 4:08 PM
To: Chuck Berking; sv-bc@eda.org
Cc: Charlie Dawson
Subject: RE: [sv-bc] FW: Mantis item filed re. force/release behavior
description

Chuck,
   1800-2008/D4 says
       A force statement to a variable shall override a procedural
assignment, continuous assignment or an
       assign procedural continuous assignment to the variable until a
release procedural statement is executed
       on the variable.

So this basically means, if I 'force' a value onto an object, I don't
care what other assignments might happen to that object elsewhere in the
design, it will be the value I 'force' until a 'release' is executed.

So, now the question is "What happens when the 'release' is executed?"

The sentence you quote below, answers that question (at least when the
target object is a variable)

If the other assignment(s) to this object elsewhere in the design are
procedural assignments, then the objects value won't change until "there
is another procedural assignment"

If the other assignment to this object elsewhere in the design is a
continuous assignment, then the objects value "shall schedule a
reevaluation of the continuous assignment driving it."

~Alex


-----Original Message-----
From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On
Behalf Of Chuck Berking
Sent: Thursday, October 25, 2007 12:22 PM
To: sv-bc@server.eda.org
Cc: Charlie Dawson
Subject: [sv-bc] FW: Mantis item filed re. force/release behavior
description

I have filed Mantis item #2152 for this, FYI.
---------------------------------------------
Sentence 3 in the 5th paragraph in "6.5 Nets and variables" reads:

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

What does this mean ??  This statement needs a rewrite at least.
---------------------------------------------
Chuck Berking
(SV-CC)

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.