From: Adam Krolnik (firstname.lastname@example.org)
Date: Fri May 06 2005 - 14:07:04 PDT
In prior sections to 13.2.2 "Using multiple library mapping files" you refer to lib.map
in the discussions, assuming (with the reader) that there exists such a file.
In this section (13.2.2) instead of saying 'a "lib.map" file can also ...", we should
say 'a library mapping file can also ..." We should consider the usage of "lib.map" and
check if the document is using that as a shorthand for "library mapping file".
We should explain explicitly the difference between the include statement and a
preprocessor include statement.
The difference being that any included (statement) library mapping file (referred to as
mapfile1) specifies verilog source files relative to the location of mapfile1.
Any included (by include compiler directive) file specifies verilog source files
relative to the original mapping file.
You may need an example of this?
OR should we exclude the `include directive?
-- 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
: Fri May 06 2005 - 13:42:58 PDT
sponsored by Boyd Technology, Inc.