Mail Archives: djgpp-workers/2003/12/23/17:09:01
--part1_16b.2801407b.2d1a16e8_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 12/23/2003 4:50:22 PM Eastern Standard Time,
rich AT phekda DOT gotadsl DOT co DOT uk writes:
> Why not just remove the definitions of is*f from <ieefp.h>?
>
> >If the changes persist into DJGPP v2.04, I will submit correcting
> >patches that restore the code. The functions to be "reverted" are
> >listed in the forwarded email and below:
> [snip]
>
> I can revert the patches I applied, once my question about <ieefp.h>
> above is answered.
>
Unfortunately, the macros suffer from what is popularly known as "legacy."
We do not know who has been using those atrocities. The fact that the macros
enable improper aliasing won't deter people who do not know better. My
suggestion is to let the macros stand in ieeefp.h and avoid their use via the patch
to fdlibml.h.
What do you think?
--part1_16b.2801407b.2d1a16e8_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><HTML><FONT SIZE=3D3 PTSIZE=3D12 FAMILY=
=3D"SERIF" FACE=3D"Georgia" LANG=3D"0">In a message dated 12/23/2003 4:50:22=
PM Eastern Standard Time, rich AT phekda DOT gotadsl DOT co DOT uk 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"=
BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 PTSIZE=3D10 F=
AMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">Why not just remove the defini=
tions of is*f from <ieefp.h>?<BR>
<BR>
>If the changes persist into DJGPP v2.04, I will submit correcting <BR>
>patches that restore the code. The functions to be "reverted" are=20=
<BR>
>listed in the forwarded email and below:<BR>
[snip]<BR>
<BR>
I can revert the patches I applied, once my question about <ieefp.h> <=
BR>
above is answered.<BR>
</BLOCKQUOTE><BR>
</FONT><FONT COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR:=20=
#ffffff" SIZE=3D3 PTSIZE=3D12 FAMILY=3D"SERIF" FACE=3D"Georgia" LANG=3D"0"><=
BR>
Unfortunately, the macros suffer from what is popularly known as "legacy."&n=
bsp; We do not know who has been using those atrocities. The fact that=
the macros enable improper aliasing won't deter people who do not know bett=
er. My suggestion is to let the macros stand in ieeefp.h and avoid the=
ir use via the patch to fdlibml.h.<BR>
<BR>
What do you think?</FONT></HTML>
--part1_16b.2801407b.2d1a16e8_boundary--
- Raw text -