Re: Verilog-AMS Committee Meeting - 12 May 2008 (Monday)

Here's the list of things we may need to discuss in committee:


Page 27 (41 of 407):
   "it shall be an error to assign a numeric value to a parameter
   declared as string or to assign a string value to an integer
   or real parameter, whether that parameter was declared as integer
   or real or had its type derived from the type of the value of the
   constant expression."

Much as I'd like the second point of that to be true (error to assign
a string value to an integer parameter), I believe 1364 Verilog treats
string literals as integers when assigning them to reg variables.


Page 61 (75 of 407):
ac_stim, white_noise, flicker_noise, noise_table were supposed to get
their own syntax item, because they are *not* analog filter functions.
See: http://www.eda-stds.org/mantis/view.php?id=2324


Page 128 (142 of 407):
The paramset examples use "nmos" which the text wants to be a
module identifier, but it's a keyword.


Page 145 (159 of 407):
fourth bullet: I suggested a rewrite of the second sentence to
   "However, parameter declaration statements shall not make out
   of module references (e.g., for setting default values)."

I believe this restriction should also apply to array port
declarations, eg
   input in[0:top.width-1];
should be disallowed.

Here's the list of things we may need to discuss in committee:


Page 27 (41 of 407):
   "it shall be an error to assign a numeric value to a parameter
   declared as string or to assign a string value to an integer
   or real parameter, whether that parameter was declared as integer
   or real or had its type derived from the type of the value of the
   constant expression."

Much as I'd like the second point of that to be true (error to assign
a string value to an integer parameter), I believe 1364 Verilog treats
string literals as integers when assigning them to reg variables.


Page 61 (75 of 407):
ac_stim, white_noise, flicker_noise, noise_table were supposed to get
their own syntax item, because they are *not* analog filter functions.
See: http://www.eda-stds.org/mantis/view.php?id=2324


Page 128 (142 of 407):
The paramset examples use "nmos" which the text wants to be a
module identifier, but it's a keyword.


Page 145 (159 of 407):
fourth bullet: I suggested a rewrite of the second sentence to
   "However, parameter declaration statements shall not make out
   of module references (e.g., for setting default values)."

I believe this restriction should also apply to array port
declarations, eg
   input in[0:top.width-1];
should be disallowed.


Page 243 (257 of 407):
Can we add an example that uses a 1800 keyword and VAMS-2.3?
Eg "logic" ?



Lastly: can we get an index?


-Geoffrey

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