Mail Archives: djgpp-workers/2003/11/05/07:56:59
--part1_2b.4a3749ff.2cda4d4b_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 11/5/2003 12:57:06 AM Eastern Standard Time,
eliz AT elta DOT co DOT il writes:
> >On the other hand, if some miscreant user decides to define an
> >identifier with the name math_errhandling, all bets are off (the behavior
> is
> >undefined).
>
> The ANSI Standard explicitly says that the name of any identifier with
> a possibly external linkage is ``reserved'', which is to say
> applications cannot use them for their own identifiers and assume
> they (the applications) will work.
>
> Imagine a program which defines an identifier named, say `malloc': is
> there any reason why it should work correctly? I don't think so.
>
You are correct, of course. I was only echoing the sense of text in ISO/IEC
9899:1999 (E), paragraph 7.12, subparagraph 9, which allows for such a
possibility:
> If a macro definition is suppressed or a program defines an identifier with
> the name math_errhandling , the behavior is undefined.
>
>
--part1_2b.4a3749ff.2cda4d4b_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D3 FAMILY=3D"SERIF" FACE=3D"=
Georgia" LANG=3D"0">In a message dated 11/5/2003 12:57:06 AM Eastern Standar=
d Time, eliz AT elta DOT co DOT il writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT><FONT COLOR=3D"#000000"=
style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"A=
rial" LANG=3D"0">>On the other hand, if some miscreant user decides to de=
fine an <BR>
>identifier with the name math_errhandling, all bets are off (the behavio=
r is <BR>
>undefined).<BR>
<BR>
The ANSI Standard explicitly says that the name of any identifier with<BR>
a possibly external linkage is ``reserved'', which is to say<BR>
applications cannot use them for their own identifiers and assume<BR>
they (the applications) will work.<BR>
<BR>
Imagine a program which defines an identifier named, say `malloc': is<BR>
there any reason why it should work correctly? I don't think so.<BR>
</BLOCKQUOTE><BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D3=
FAMILY=3D"SERIF" FACE=3D"Georgia" LANG=3D"0"><BR>
You are correct, of course. I was only echoing the sense of text in IS=
O/IEC 9899:1999 (E), paragraph 7.12, subparagraph 9, which allows for such a=
possibility:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT><FONT COLOR=3D"#000000"=
style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 FAMILY=3D"SANSSERIF" FACE=3D"A=
rial" LANG=3D"0">If a macro definition is suppressed or a program defines an=
identifier with the name math_errhandling , the behavior is undefined.<BR>
<BR>
</BLOCKQUOTE><BR>
<BR>
</FONT></HTML>
--part1_2b.4a3749ff.2cda4d4b_boundary--
- Raw text -