Shalom, I agree the editor has a tremendously difficult job, and we all have room for improvement in our reviewing efforts. But I'm wondering a bit about the process by which those annotated questions disappear from the drafts. In Draft3a, the text in question is still blue in color, but the question in the margin is gone. In Draft4, the text is black. Did someone actually answer this question and lead the editor to believe that the added text was correct? If not, I would favor requesting that the editor leave those questions in the LRM until answered by some "suitable quorum" of folks from one of the committees. We were lucky to catch this inconsistency introduced solely as part of the merge. Thanks, Doug From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Bresticker, Shalom Sent: Thursday, October 11, 2007 6:04 AM To: Rich, Dave; sv-bc@server.eda.org Subject: RE: [sv-bc] release/deassign with variables driven by continuous assignments Dave, I agree with your conclusion. But I think the text in 6.5 is unclear. It should say something to the effect that if the variable is driven by a continuous assignment, then as you say, deassign/release of the variable will cause an immediate re-evaluation of the continuous assignment. 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. Note that the extra text in 10.6.1 and 10.6.2, "or the next time a continuous assignment driving the variable is evaluated," was added by the editor in the LRM merge in an attempt to update the 1364 text to SystemVerilog. The editor added his question on the side from the very beginning, so it is not his fault that this text has remained till now. Thanks, Shalom ________________________________ From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Rich, Dave Sent: Thursday, October 11, 2007 6:59 AM To: sv-bc@server.eda.org Subject: [sv-bc] release/deassign with variables driven by continuous assignments In section 10.6.1 there is a question from the editor: Does the result of a cont. assign to a variable update immediately when the variable is released? The answer is in 6.5 "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." and probably should have been moved to 10.6 So the text in 10.6.1 and 10.6.2 is incorrect. It will schedule an evaluation upon release, not wait for the next event that causes an evaluation. I thought someone, Shalom perhaps, already made up a list of editor's questions as a mantis item, but I could not find it. Dave -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , 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 <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.Received on Thu Oct 11 08:27:02 2007
This archive was generated by hypermail 2.1.8 : Thu Oct 11 2007 - 08:27:30 PDT