From: Shalom Bresticker (Shalom.Bresticker@motorola.com)
Date: Mon Jun 17 2002 - 22:00:21 PDT
Precedence: bulk
This is the full posting from comp.lang.verilog.
Shalom
-------- Original Message --------
Subject: block_comments in libmap files
Date: Sun, 16 Jun 2002 01:17:08 GMT
From: Ole <olsonville@mindspring.com>
Organization: Prodigy Internet http://www.prodigy.com
Newsgroups: comp.lang.verilog
The verilog 2001 standard Library Source Text
(libmap files) may contain library_declarations.
Some examples from the standard:
library gateLib ./*.vg;
library lib4 "/proj/lib1/*ver.v";
The grammar also defines the standard
/* block_comment */
It is not clear how to parse this:
library lib ./rtl/*comment*/foo.v
Do we assume that
1. block_comments can be consumed by the lexer
and that the first example in the standard is
wrong and should have quotes because is has '/*':
library gateLib "./*.vg";
or 2. block comments must be "parsed" and block_comments
are not allowed in a file_path_spec
or 3. block_comments are not allowed in lib.map files
===
On a side note, does it seems that several assumptions
need to be made to make the library declarations
workable in a real environment:
1. paths ending with /*.v (wildcard anywhere in
the base of the filename) contain only the
module with the name matching the filename base.
2. paths with a wildcard in the extension
must match a "default verilog" filename extension
and only contain the module with the name matching
the filename.
Filenames with no wildcards can contain any verilog.
Otherwise you would be parsing a LOT of files you don't
need to. (expecially with the '...' being legal)
// the verilog module is in some file, somewhere in the filesystem
library all "/.../*";
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:55:37 PDT
and
sponsored by Boyd Technology, Inc.