Hi, The syntax of clocking_event in Syntax 14-1 is clocking_event ::= @ identifier | @ ( event_expression ) The parallel syntax of event_control is event_control ::= @ hierarchical_event_identifier | @ ( event_expression ) | @* | @ (*) | @ ps_or_hierarchical_sequence_identifier The clocking_event syntax has @identifier whereas event_control has @hierarchical_event_identifier. The question is whether it is deliberate that clocking_event does not allow hierarchical identifiers without parentheses. The text does not seem to say anything about it, and hierarchical identifiers would be allowed anyway by adding parentheses. The event_control syntax in V2K1 also only allowed a non-hierarchcial identifier without parentheses. This was changed in V2K5, as described in http://boyd.com/1364_btf/report/full_pr/182.html. In short, the syntax was changed to conform to de facto tool behavior. Note that the BNF non-terminal is called an event_identifier, but it is not limited to variables of event type. Thanks, Shalom Shalom Bresticker Intel LAD DA, Jerusalem, Israel +972 2 589 6582 (office) +972 54 721 1033 (cell) http://www.linkedin.com/in/shalombresticker --------------------------------------------------------------------- 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 Mon Jan 4 05:32:08 2010
This archive was generated by hypermail 2.1.8 : Mon Jan 04 2010 - 05:33:06 PST