From: Adam Krolnik (firstname.lastname@example.org)
Date: Mon May 09 2005 - 15:42:57 PDT
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 implementation with
optional semicolons (and it works) then is optional semicolon's too far out?
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"
This archive was generated by hypermail 2.1.4
: Mon May 09 2005 - 15:18:29 PDT
sponsored by Boyd Technology, Inc.