From: Pragmatic C Software (sjmeyer@pragmatic-c.com)
Date: Tue Apr 26 2005 - 08:31:33 PDT
Quoting Steven Sharp (sharp@cadence.com):
> Mark Hartoog wrote:
> >In the section on libraries (13.2.1 in 1364-2001) it says "When parsing
> >a source description file (or files), the parser shall first read the
> >library mapping information from a pre-defined file prior to reading
> >any source files." This implies that library mapping files are NOT
> >source files.
>
> FWIW:
> Looking at the BNF again, I see that section A.1.1 describing library
> map files is titled "Library source text". That tends to indicate that
> they are source files.
Interesting, I read the phrase 'Library source text' as source text
for the config library control feature just as 'linker source text' in
programming means the text in the separate (with different syntax) linker
control source file. No one would interpret 'linker source text' as linker
control commands that go in .c files.
I hope that Verilog will continue to support all types of users and
adding things like special keywords that control which parsing algorithm
is used is very bad for our small company type users who are not able
to hire people who just maintain libraries and can't affort to pay
for training. I think anything such as requiring separate files for
configs or such as allowing designers who want to run just old XL style
Verilog to not need to do any extra work is good. Just my two cents.
/Steve
-- Steve Meyer Phone: (612) 371-2023 Pragmatic C Software Corp. email: sjmeyer@pragmatic-c.com 80 South 8th Street, Suite 900 Minneapolis, MN 55402
This archive was generated by hypermail 2.1.4
: Tue Apr 26 2005 - 08:10:39 PDT
and
sponsored by Boyd Technology, Inc.