RE: [sv-bc] E-mail Ballot Due Dec 17 8AM PST

From: Bresticker, Shalom <shalom.bresticker_at_.....>
Date: Thu Dec 13 2007 - 02:21:24 PST
Doug,


	SVDB 1602 ___Yes   X__No 
	http://www.eda.org/svdb/view.php?id=1602 

	On 1602, I found some minor typos in the example in the
proposal:

	task t1 (output o = a) ; // default binds to m.a

	...

	endtask :a

	task t2 (output o = b) ; // illegal, b cannot be resolved

	...

	endtask :b

	Observe the labels after the endtask keywords.
	The first should be :t1 and the second should be :t2.

	[SB] OK

	 Also, after all the discussion in the Mantis bug notes, I would
like
	to see an example using a default for an inout formal argument.
	Just to be crystal clear on the semantics.
	[SB] OK 

	If the above two points are addressed, I will change my vote to
YES.

	SVDB 2097 _X_Yes   ___No 
	http://www.eda.org/svdb/view.php?id=2097 

	I vote Yes, but the grammar at the very end of the proposal is a
bit rough (See below)
	There should be no hyphen between "shall" and "maintain".  And
at the very end of the
	sentence, there should probably be an "is executed."

	When released, then if the variable is not driven by a
continuous assignment and does not currently have an active assign
procedural continuous assignment, the variable shall not immediately
change value and shall maintain its current value until the next
procedural assignment.
	[SB] I don't see a problem with the grammar. The hyphen is a
problem with Word, I'll try again to remove it. (There is also one in
"assign procedural".) The "next procedural assignment" comes from the
original text, but I will change it to "and shall maintain its value
until the next procedural assignment to the variable is executed". OK?

	Thanks,

	Shalom

---------------------------------------------------------------------
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.
Received on Thu Dec 13 03:08:38 2007

This archive was generated by hypermail 2.1.8 : Thu Dec 13 2007 - 03:09:10 PST