Re: enhancement/350: PROPOSAL - Deprecate configs in Verilog source

From: Steven Sharp (sharp@cadence.com)
Date: Wed May 12 2004 - 13:30:00 PDT

  • Next message: Jayaram Bhasker: "RE: enhancement/350: PROPOSAL - Deprecate configs in Verilog source"

    The following reply was made to PR enhancement/350; it has been noted by GNATS.

    From: Steven Sharp <sharp@cadence.com>
    To: sharp@cadence.com, Shalom.Bresticker@freescale.com
    Cc: btf-bugs@boyd.com
    Subject: Re: enhancement/350: PROPOSAL - Deprecate configs in Verilog source
    Date: Wed, 12 May 2004 16:41:01 -0400 (EDT)

    >> The keyword <incdir> is removed from the Verilog HDL keywords, but is
    >> not added to the library mapping file keywords. This is because the
    >> syntax does not appear to require reserving <incdir> because it always
    >> appears after a hyphen. However, it could still be added to the list
    >> of library mapping file keywords if desired.
    >
    >This is related to the question of whether white space is allowed between
    >the hyphen and <incdir>. If not, what is the lexical token here?
     
     Agreed. If no white space is allowed, then the token is <-incdir> and
     <incdir> is not a reserved word. If white space is allowed, then the
     tokens are the hyphen and <incdir>, which is presumably a reserved word.
     
     I don't know where the hyphen syntax came from or why the hyphen is there
     (and the LRM doesn't even say what -incdir means). The <library> syntax
     looks like a command line in a script, while the config syntax looks more
     Verilog-like.
     
     If we assume that it is based on Unix command line syntax, then no white
     space would be allowed after the hyphen. The BNF seems to imply that it
     is all one token also.
     
     Steven Sharp
     sharp@cadence.com
     

    This archive was generated by hypermail 2.1.4 : Wed May 12 2004 - 13:30:26 PDT and
    sponsored by Boyd Technology, Inc.