[sv-ac] Re: Email Ballot due June 25th

Hi Ed,

3525 introduces another backward incompatibility for the property_case_item in the case .. endcase. Current LRM has property_statement in property_case_item which requires semi-colon after property_expr. However the proposal has property_expr (without ‘;’). Is this intended to make it consistent with if .. else ? If yes, then you need to add a note regarding this and will also need to modify the example for the case .. endcase property. If not then this can be fixed by changing property_case_item to include ‘;’ in the proposal. Something like
property_case_item::=
expression_or_dist { , expression_or_dist } : property_expr ;
| default [ : ] property_expr ;

Anupam

On Jun 24, 2012, at 6:58 AM, "Bresticker, Shalom" <shalom.bresticker@intel.com<mailto:shalom.bresticker@intel.com>> wrote:

I'm not qualified to say, but I wanted to make sure that people are aware of it.

Regards,
Shalom

Also, it should be noted that moving the if and case constructs to property_expr allows them wherever property_expr would be allowed, such as in property_actual_arg (Syntax 16-16).
That would be actually more appropriate, it seems to me. Is something wrong with that?
---------------------------------------------------------------------
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.
Received on Mon Jun 25 00:20:04 2012