Re: errata/175: PROPOSAL - 13.2: file_path_spec syntax andrelated issues

From: Shalom.Bresticker@motorola.com
Date: Fri Apr 11 2003 - 04:30:02 PDT

  • Next message: Shalom.Bresticker@motorola.com: "Re: errata/325: 12.4 confused on hierarchy for automatics"

    Precedence: bulk

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

    From: Shalom.Bresticker@motorola.com
    To: Anders Nordstrom <asic@sympatico.ca>
    Cc: etf-bugs@boyd.com
    Subject: Re: errata/175: PROPOSAL - 13.2: file_path_spec syntax andrelated
     issues
    Date: Fri, 11 Apr 2003 14:28:03 +0300 (IDT)

     The original mail on this is quoted at the bottom.
     
    > Date: Wed, 15 Jan 2003 09:22:15 +0200
    > Anders Nordstrom wrote:
    > > The missing semicolon was a typo. Update the proposal to:
    > > include_statement ::= file_path_spec; | "file_path_spec";
    > > This addresses part A.
     
     Since file_path_spec appears 5 times and file_path only once, I suggest:
     
     A,B: include_statement ::= include file_path_spec ; ('include' and ';' in bold)
          file_path_spec ::= file_path | "file_path" (double-quotes are real)
     
    > > Part B is addressed by errata/99
     
     99 talks about keywords. I don't see the connection.
     
    > > and part D by errata/135.
     
     Again, what is the connection?
     
    > > Part C: Absolute and relative paths are common terms. I am OK with "/",
    > > what is a more common name for the top directory or root?
     
     What about systems which use \ instead of / ?
     
    > > Part E: errata/99 proposes a list of special keywords.
    > > Syntax 13-2 already lists -incdir as one word (the - is bold as well).
     
     That was exactly my question. Can there be a space between - and incdir?
     
     Anders also suggested adding the following:
     "Add Note 3 under NOTES just after Syntax 13-2:
     The " " in file_path_spec are optional if the file_path only contains the
     characters a-z, A-Z, 0-9 or . , otherwise they are required."
     
     What about characters _-/\?* ? Most of these appear in examples in the LRM.
     
     Shalom
     
     Original mail:
      
    > Date: Sun, 27 Oct 2002 18:06:51 +0200
    > From: Shalom Bresticker <Shalom.Bresticker@motorola.com>
    > Subject: errata/175: 13.2: file_path_spec syntax and related issues
    >
    > file_path_spec is used in library declarations,
    >
    > Issues:
    >
    > A. Whereas in library_declaration BNF, it appears simply as
    > file_path_spec, it appears as <file_path_spec> in include_statement.
    > There does not seem to be any reason for the angle brackets.
    >
    > B. The production file_path_spec ::= file_path appears to serve no
    > useful purpose. The two appear to be synonymous. file_path seems to be
    > used only here.
    >
    > C. The NOTE following Syntax 13-2 starts,
    > "The file_path uses file system-specific notation to specify an absolute
    > or relative path to a particular file or set of files."
    > Yet it talks about "/". Is that really common to all systems?
    >
    > D. Related to errata/99 about library keywords, note that "incdir" can
    > be used only as "-incdir", and the "-" may only be followed by "incdir",
    > making it even less of a "general" keyword.
    >
    > E. Can there be white space between "-" and "incdir"?
    >
    > F. There should be examples of use of "-incdir" and of "include".
    >
    > G. See related issues 99, 135.
     
     --
     Shalom Bresticker Shalom.Bresticker@motorola.com
     Design & Reuse Methodology Tel: +972 9 9522268
     Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890
     POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478
     
     
     
     
     
     

    This archive was generated by hypermail 2.1.4 : Fri Apr 11 2003 - 04:34:48 PDT and
    sponsored by Boyd Technology, Inc.