RE: [sv-ec] Mantis 2279 (randomize syntax feedback)

Thanks, Jonathan. Comments below: 

> I've written a very short proposal that I hope responds to 
> the Champions' feedback on 1858 (name resolution in 
> randomize...with), and have uploaded it to Mantis 2279.  

1. If all three are the same construct and the A.8.2 BNF is changed as
in the proposal, then I don't see why the two syntax boxes in Clause 17
should be inventing new non-terminals with new names and saying that
they are not in Annex A. 

It's true that the scope_randomize in Syntax 17-10 is a reduced form
that omits all the non-relevant parts, but the
inline_constraint_declaration in Syntax 17-9 seems exactly the same
except for the prefixed class_variable_identifier. I don't think that
justifies a new syntax and a new name for the non-terminal.


2. The scope_randomize in Syntax 17-10 allows [std::]. The BNF in A.8.2
does not seem to allow it with the prefix, only if you prefix it with [
package_scope ] as tf_call allows you to do, but not via randomize_call.


3. The description of std::randomize() appears also in G.4 with yet
another syntax:

randomize( variable_identifier {, variable_identifier } )
[ with constraint_block ];

I'd like to see the syntax be consistent throughout.
Note that scope_randomize in Syntax 17-10 also allows an empty
variable_identifier_list whereas this syntax does not. 17.12 says, "If
the scope randomize function is called with no arguments, then it
behaves as a checker and simply returns status." What does "behave as a
checker" mean? What status does it return?

The syntax in G.4 also should not end in a semicolon, I think.


4. I think the two footnotes in the BNF in the proposal should be
combined into a single footnote at the end of the production.


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.