- Previous message: Shalom Bresticker: "[Fwd: [sv-ec] Scheduling Semantics proposal]"
- Maybe in reply to: etf@boyd.com: "errata/175: PROPOSAL - 13.2: file_path_spec syntax and related issues"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Precedence: bulk
The following reply was made to PR errata/175; it has been noted by GNATS.
From: Anders Nordstrom <asic@sympatico.ca>
To: <etf-bugs@boyd.com>
Cc:
Subject: Re: errata/175: PROPOSAL - 13.2: file_path_spec syntax and
related issues
Date: Tue, 14 Jan 2003 21:26:02 -0500
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3125424363_17178000
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
The missing semicolon was a typo. Update the proposal to:
include_statement ::=3D file_path_spec; | "file_path_spec";
This addresses part A. Part B is addressed by errata/99 and part D by
errata/135.
Part C: Absolute and relative paths are common terms. I am OK with =B3/=B2, wha=
t
is a more common name for the top directory or root?
Part E: errata/99 proposes a list of special keywords. Syntax 13-2 already
lists =ADincdir as one word (the =AD is bold as well).
Regards,
Anders
On 1/13/03 10:40 PM, "Shalom.Bresticker@motorola.com"
<Shalom.Bresticker@motorola.com> wrote:
> Precedence: bulk
>=20
> The following reply was made to PR errata/175; it has been noted by GNATS=
.
>=20
> From: Shalom.Bresticker@motorola.com
> To: etf-bugs@boyd.com
> Cc: =20
> Subject: Re: errata/175: PROPOSAL - 13.2: file_path_spec syntax and relat=
ed
> issues
> Date: Tue, 14 Jan 2003 05:35:18 +0200 (IST)
>=20
> Does this proposal address all issues raised in 175? Probably not.
> =20
>> > include_statement ::=3D file_path_spec; | "file_path_spec"
> =20
> What about semicolon if quotes are used?
> =20
--B_3125424363_17178000
Content-type: text/html; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: errata/175: PROPOSAL - 13.2: file_path_spec syntax and related i=
ssues</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana">The missing semicolon was a typo. Update the proposal =
to:<BR>
</FONT><FONT FACE=3D"Monaco"><TT>include_statement ::=3D file_path_spec; | &quo=
t;file_path_spec";<BR>
</TT></FONT><FONT FACE=3D"Verdana"><BR>
This addresses part A. Part B is addressed by errata/99 and part D by errat=
a/135.<BR>
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?<BR>
Part E: errata/99 proposes a list of special keywords. Syntax 13-2 already =
lists –incdir as one word (the – is bold as well). <BR>
<BR>
Regards,<BR>
<BR>
Anders<BR>
<BR>
<BR>
<BR>
On 1/13/03 10:40 PM, "Shalom.Bresticker@motorola.com" <Shalom.=
Bresticker@motorola.com> wrote:<BR>
<BR>
</FONT><BLOCKQUOTE><FONT FACE=3D"Monaco"><TT>Precedence: bulk<BR>
<BR>
The following reply was made to PR errata/175; it has been noted by GNATS.<=
BR>
<BR>
From: Shalom.Bresticker@motorola.com<BR>
To: etf-bugs@boyd.com<BR>
Cc: <BR>
Subject: Re: errata/175: PROPOSAL - 13.2: file_path_spec syntax and related=
<BR>
issues<BR>
Date: Tue, 14 Jan 2003 05:35:18 +0200 (IST)<BR>
<BR>
Does this proposal address all issues raised in 175? Probably not.<BR=
>
<BR>
> include_statement ::=3D file_path_spec; | "file_path_spec&quo=
t;<BR>
<BR>
What about semicolon if quotes are used?<BR>
<BR>
</TT></FONT></BLOCKQUOTE><FONT FACE=3D"Monaco"><TT><BR>
</TT></FONT>
</BODY>
</HTML>
--B_3125424363_17178000--
- Next message: Shalom Bresticker: "Re: errata/175: PROPOSAL - 13.2: file_path_spec syntax andrelated issues"
- Previous message: Shalom Bresticker: "[Fwd: [sv-ec] Scheduling Semantics proposal]"
- Maybe in reply to: etf@boyd.com: "errata/175: PROPOSAL - 13.2: file_path_spec syntax and related issues"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
This archive was generated by hypermail 2.1.4
: Tue Jan 14 2003 - 18:31:35 PST
and
sponsored by Boyd Technology, Inc.