[sv-bc] Re: [sv-ec] Peculiar BNF for hierarchical_btf_identifier

From: Surya Pratik Saha <spsaha@cal.interrasystems.com>
Date: Fri Apr 30 2010 - 06:53:23 PDT

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>
To: Surya Pratik Saha <spsaha@cal.interrasystems.com>, sv-ec@eda.org <sv-ec@eda.org>, sv-bc@eda.org <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] On Behalf Of Surya Pratik Saha
Sent: Friday, April 30, 2010 4:11 PM
To: sv-ec@eda.org; 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, 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 Fri Apr 30 06:54:01 2010