From: Brad Pierce (Brad.Pierce@synopsys.com)
Date: Mon May 09 2005 - 16:09:31 PDT
I would recommend against reordering the subclauses of A.1.
It makes it hard to compare different versions of the LRM. But if A.1
is reordered, then the associated Syntax boxes that excerpt A.1 need to
be updated, too --
Syntax 3-4, 3-5, 3-6
Syntax 12-1, 12-2, 12-3, 12-5
Syntax 13-5, 13-6, 13-7
But please consider just not changing the ordering. The number of
Syntax boxes that would need to be changed in the SV LRM is much longer.
Also, I agree with Adam about the optionality of semicolons.
The semicolons are redundant and the 2001 BNF does not require them.
Requiring them now breaks backward compatibility.
From: firstname.lastname@example.org [mailto:email@example.com]On Behalf Of Adam
Sent: Monday, May 09, 2005 3:43 PM
To: Fitzpatrick, Tom
Cc: firstname.lastname@example.org; email@example.com; firstname.lastname@example.org; email@example.com;
Subject: Re: Special 1364 Meeting to resolve Issue 680 (Configs)
I will most likely be late to this discussion, sorry.
All this does is:
o move config from library source to verilog source
o make semicolon's mandatory in some places
If optional quotes are being considered and there exists an
optional semicolons (and it works) then is optional semicolon's too far
The examples of filename specification and expansion should use quotes on
filenames to match what a user must specify. E.g.
/proj/lib*/*/a.v = /proj/lib1/rtl/a.v, /proj/lib2/gates/a.v
Propose (quote wildcarding)
"/proj/lib*/*/a.v" = /proj/lib1/rtl/a.v, /proj/lib2/gates/a.v
Etc. for the remaining examples with wildcards.
-- Adam Krolnik ZSP Verification Mgr. LSI Logic Corp. Plano TX. 75074 Co-author "Assertion-Based Design"
This archive was generated by hypermail 2.1.4
: Mon May 09 2005 - 15:45:02 PDT
sponsored by Boyd Technology, Inc.