Hi,
I agree with Surya, the rule "hierarchical_identifier [ class_scope ] method_identifier", mentioned in LRM has no meaning , only then the first variable is optional and followed by "." delimiter, as Shalom advised)
1) we need delimiter after "hierarchical_identifier" to connect it to its followers.
2) "class scope" already contains kind of "hierarchical_identifier" - "] class_identifier" in its beginning.
3) there is no meaning "hierarchical_identifier" following by "class_scope"
4) hierarchical_identifier has more ability, for example it can contain "constant_bit_select", which is not exists in "ps_class_identifier"
hierarchical_identifier ::= [ $root . ] { identifier constant_bit_select . } identifier
The "class_scope" rules are
class_scope ::= class_type ::
class_type ::=
ps_class_identifier [ parameter_value_assignment ]
{ :: class_identifier [ parameter_value_assignment ] }
ps_class_identifier ::= [ package_scope ] class_identifier
Thanks,
Irina Lavva
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of Surya Pratik Saha
Sent: Friday, April 30, 2010 5:16 PM
To: Bresticker, Shalom
Cc: sv-ec@eda.org; sv-bc@eda.org
Subject: Re: [sv-ec] Peculiar BNF for hierarchical_btf_identifier
OK,
I have filed Mantis 3065 with this mail trail link.
Regards
Surya
-------- Original Message --------
Subject: Re:[sv-ec] Peculiar BNF for hierarchical_btf_identifier
From: Bresticker, Shalom <shalom.bresticker@intel.com><mailto:shalom.bresticker@intel.com>
To: Surya Pratik Saha <spsaha@cal.interrasystems.com><mailto:spsaha@cal.interrasystems.com>
Cc: "sv-ec@eda.org"<mailto:sv-ec@eda.org> <sv-ec@eda.org><mailto:sv-ec@eda.org>, "sv-bc@eda.org"<mailto:sv-bc@eda.org> <sv-bc@eda.org><mailto:sv-bc@eda.org>
Date: Friday, April 30, 2010 7:38:35 PM
I know of no Mantis on this.
As far as I can see, the origin of this syntax is in http://www.eda.org/sv-ec/Extensions/EXT_16_tf_event_control_v1.pdf, from September 15, 2003.
Shalom
________________________________
From: Surya Pratik Saha [mailto:spsaha@cal.interrasystems.com]
Sent: Friday, April 30, 2010 4:53 PM
To: Bresticker, Shalom
Cc: sv-ec@eda.org<mailto:sv-ec@eda.org>; sv-bc@eda.org<mailto:sv-bc@eda.org>
Subject: Re: [sv-ec] Peculiar BNF for hierarchical_btf_identifier
Thanks Shalom,
Do you know there is already a Mantis regarding this? If not, then I will file a new one.
Regards
Surya
-------- Original Message --------
Subject: Re:[sv-ec] Peculiar BNF for hierarchical_btf_identifier
From: Bresticker, Shalom <shalom.bresticker@intel.com><mailto:shalom.bresticker@intel.com>
To: Surya Pratik Saha <spsaha@cal.interrasystems.com><mailto:spsaha@cal.interrasystems.com>, sv-ec@eda.org<mailto:sv-ec@eda.org> <sv-ec@eda.org><mailto:sv-ec@eda.org>, sv-bc@eda.org<mailto:sv-bc@eda.org> <sv-bc@eda.org><mailto:sv-bc@eda.org>
Date: Friday, April 30, 2010 7:09:59 PM
Maybe
[ hierarchical_identifier . | class_scope ] method_identifier
Shalom
________________________________
From: owner-sv-ec@eda.org<mailto:owner-sv-ec@eda.org> [mailto:owner-sv-ec@eda.org] On Behalf Of Surya Pratik Saha
Sent: Friday, April 30, 2010 4:11 PM
To: sv-ec@eda.org<mailto:sv-ec@eda.org>; sv-bc@eda.org<mailto:sv-bc@eda.org>
Subject: [sv-ec] Peculiar BNF for hierarchical_btf_identifier
Hi,
SV 2009 LRM defines the rule of hierarchical_btf_identifier in the following way:
hierarchical_btf_identifier ::=
hierarchical_tf_identifier
| hierarchical_block_identifier
| hierarchical_identifier [ class_scope ] method_identifier
But what is the meaning of "hierarchical_identifier [ class_scope ] method_identifier"?
There is a LRM text (Page 485) section 19.3 "Defining the coverage model: covergroup":
Block event expressions that specify the begin keyword followed by a hierarchical identifier denoting a named block, task, function, or class method shall be triggered immediately before the corresponding block, task, function, or method begins executing its first statement.
So I think the rule should be:
| hierarchical_identifier
| [ class_scope ] method_identifier
Please let me know.
-- Regards Surya -- This message has been scanned for viruses and dangerous content by MailScanner<http://www.mailscanner.info/>, and is believed to be clean. --------------------------------------------------------------------- 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. --------------------------------------------------------------------- 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<http://www.mailscanner.info/>, and is believed to be clean. --------------------------------------------------------------------- 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 Sun May 2 00:54:51 2010
This archive was generated by hypermail 2.1.8 : Sun May 02 2010 - 01:00:16 PDT