From: Dennis Marsa (firstname.lastname@example.org)
Date: Fri May 03 2002 - 14:29:08 PDT
Adam Krolnik wrote:
> Precedence: bulk
> Hello Jayaram;
> The specifications do not include double quotes to specify
> filenames. Since the library mapping file deals with mostly
> filenames, we saw no need to require quoted filenames.
> Example 13.7.3 incorrectly specifies quotes when should not
> be specified.
Yet, the include_statement production shown in the
Syntax 13-2 box on page 201 requires an include file
name be delimited with <>!
Anyway, wouldn't some sort of delimiter be necessary for
certain kinds of filenames in library statements?
The syntax for the library statement specifies using ',' to
separate file paths.
But, ',' is a valid character that can be used in a filename.
library mylib foo.v,bar.v
Does the above map 2 files, or 1 file to mylib?
Also, blanks can be used in filenames as well. Without
using a wildcard, wouldn't one need some sort of delimiter
in order to specify a file containing blanks?
library mylib < foo.v>
If not required, perhaps <> delimiters should be an option in
library file path specifications?
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:55:36 PDT
sponsored by Boyd Technology, Inc.