I agree. Thanks for sharing the comment. Kanaparty Rao. ----- Original Message ----- From: "Swapnajit Chakraborti" <swapnaj@cadence.com> To: <Neil.Korpusik@Sun.com>; <sv-ec@eda.org> Sent: Monday, August 08, 2005 12:39 AM Subject: Re: [sv-ec] Re: [sv-bc] coverage_type_option_assignment >I sent a similar query on Accellera 3.1a draft long back > (see below). > > Thx, > Swapnajit. > > > >> ------------------------------------------------------------------------ >> >> Subject: [sv-bc] coverage_type_option_assignment >> Date: Fri, 05 Aug 2005 08:49:56 -0700 >> From: Paul Graham <pgraham@cadence.com> >> To: sv-bc@eda.org >> >> I'm looking at p1800 draft 6. >> >> The syntax for coverage_type_option_assignment appears in >> section 18.6.1, but nowhere else. The 18-6 syntax box has a >> comment "not in Annex A". What is the reason for this >> dangling piece of syntax? Is it part of the language? >> >> Paul > > -------- Original Message -------- > Subject: [sv-ec] covergroup option/type_option assignment > Date: Tue, 22 Feb 2005 19:09:59 +0530 > From: Swapnajit Chakraborti <swapnaj> > Organization: Cadence Design Systems > To: sv-ec@eda.org > > Section 20.6 of LRM mentions that options of a covergroup > instance can be set procedurally. > > Example: > -------- > cg cg1 = new; > ... > cg1.option.weight = 3; > > In similar fashion, type_options for covergroup declaration > can also be set procedurally (section 20.6.1). > > Example: > -------- > cg::type_option.weight = 5; > > Syntax 20-5 (page 321) and Syntax 20-6 (page 323) > of LRM, also describe the BNF for these assignment > statements. But these rules donot appear in Annex A > as well as in http://www.eda.org/sv/SV3.1a_bnf_no_footnotes.htm. > > Any specific reason for this? > > Thx, > Swapnajit.Received on Sun Aug 7 22:49:56 2005
This archive was generated by hypermail 2.1.8 : Sun Aug 07 2005 - 22:50:03 PDT