From: sharp@cadence.com
Date: Mon May 19 2003 - 17:18:44 PDT
Precedence: bulk
>Number: 350
>Category: enhancement
>Originator: sharp@cadence.com
>Environment:
>Description:
Verilog-2001 allows configs to appear in either Verilog
source files, or the library map file. I am proposing
that they not be allowed in Verilog source files, only
in the library map file.
The main reason for proposing this is that configs use
a lot of reserved keywords that can create backward
compatibility problems for existing designs. A test on
a large set of real customer designs indicated that 15%
of them would not compile with these keywords reserved.
And before anyone suggests context-sensitive keywords
(blech!), the main offender was the keyword "config",
which marks the start of the context and therefore
can't be context-sensitive.
The idea of having configs in the source code presumably
came from VHDL. Most experienced Verilog people I have
consulted agree that Verilog source files should only
contain real Verilog source, and that configs should be
put in a side file. The existing standard already allows
for them to be put into the library map file, which fits
that description nicely.
Nor is putting configs in the Verilog source file the
most beneficial use model. If you want to change what are
effectively "link" options, you don't want to have to
change and recompile the source code each time. My
inquiries indicate that VHDL users most often supply
configs in separate files, usually generated by tools
and at most tweaked by hand. So this seems to be the
most natural way of using them anyway.
If we do deprecate this, it would be best to do it
soon and publicize it before it comes into wide use.
This archive was generated by hypermail 2.1.4
: Mon May 19 2003 - 17:20:50 PDT
and
sponsored by Boyd Technology, Inc.