From: Adam Krolnik (krolnik@lsil.com)
Date: Wed Aug 15 2001 - 13:20:01 PDT
The following reply was made to PR errata/16; it has been noted by GNATS.
From: Adam Krolnik <krolnik@lsil.com>
To: btf-bugs@boyd.com
Cc: btf@boyd.com
Subject: Re: errata/16: 19.7 `line - meaning of level parameter is unclear
Date: Wed, 15 Aug 2001 15:13:55 -0500
So many questions... all in my archives somewhere...
>- The worst is the "level" parameter, which is a CPP output ! It is not a
>user directive at all ! It is INFORMATION
> for the compiler which DESCRIBES the file hierarchy, not CONTROLLING it. >Even worse, it became a REQUIRED parameter in 1364-2001. No
> wonder I did not understand its meaning and use in 1364!
> - Why is "filename" required ? Neither CPP nor Gnu CPP require it ! I >might want to use the same file
> in different places under different names. I should not have to play with >this directive each time.
This came up in the discussions. To simplify parsing, all parameters
became required. Since this directive was envisioned to be used by a
source code generator (preprocessor, source to source translator, etc.)
the requirement of the parameters was not considered a hardcase. You are
correct, it is not controlling anything; nor would you want it to.
> - The Gnu CPP man page says that "filename" is a string constant. >Neither CPP nor Gnu CPP say that "filename" can be a full or
> relative path name. Why here ? (I'm devil's advocate here.) What happens
> if "filename"
> is something like ".." ? Is the Verilog compiler/interpreter supposed to
>relate to this as just a filename or is it supposed to interpret file
>location as well ?
The filename is a string - whatever you want to put there. The
compiler's
only use for this data is to inform the user of something pertaining
to it. So your filename could be any of your examples. What the user
puts in is what he will get out.
Adam Krolnik
Verification Mgr.
LSI Logic Corp.
Plano TX. 75074
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:54:44 PDT
and
sponsored by Boyd Technology, Inc.