[sv-bc] Re: Special 1364 Meeting to resolve Issue 680 (Configs)

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.

-- Brad

-----Original Message-----
From: owner-etf@boyd.com [mailto:owner-etf@boyd.com]On Behalf Of Adam
Krolnik
Sent: Monday, May 09, 2005 3:43 PM
To: Fitzpatrick, Tom
Cc: etf@boyd.com; btf@boyd.com; sv-champions@eda.org; sv-cc@eda.org;
sv-bc@eda.org
Subject: Re: Special 1364 Meeting to resolve Issue 680 (Configs)




Hello all;

I will most likely be late to this discussion, sorry.

For Configs_4.pdf:
   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
implementation with
   optional semicolons (and it works) then is optional semicolon's too far
out?


For Config.pdf:

   The examples of filename specification and expansion should use quotes on
the wildcard
   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"