X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f From: Kbwms AT aol DOT com Message-ID: <16b.2801407b.2d1a16e8@aol.com> Date: Tue, 23 Dec 2003 17:08:40 EST Subject: Re: isnanf et al To: djgpp-workers AT delorie DOT com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_16b.2801407b.2d1a16e8_boundary" X-Mailer: 8.0 for Windows sub 6021 Reply-To: djgpp-workers AT delorie DOT com --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 ? > > >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 > 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 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 defini= tions 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=20=
>listed in the forwarded email and below:
[snip]

I can revert the patches I applied, once my question about <ieefp.h> <= BR> above is answered.

<= 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.

What do you think? --part1_16b.2801407b.2d1a16e8_boundary--