From: Steven Sharp (email@example.com)
Date: Mon Jun 17 2002 - 16:11:00 PDT
This was in a posting in comp.lang.verilog, so I thought I would run it past
some people who might know the answers:
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
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
sponsored by Boyd Technology, Inc.