Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E775B18.5E9CA18D@phekda.freeserve.co.uk>
Date: Tue, 18 Mar 2003 17:44:56 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: strto{d,f,ld}, inf and nan patch
References: <200303180839 DOT JAA03639 AT lws256 DOT lu DOT erisoft DOT se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Martin Stromberg wrote:
> 
> Eli said:
[snip]
> > Ideally, we should also generate the precise bit pattern as given by
> > <anything>.  It cannot be too hard.
> 
> Yes. All we need to agree on the format and if somebody else does the
> printing part, I'll do the strto{f,d,ld}() part.
[snip]

If no-one else volunteers (seems unlikely), then I'll do the printing part.
Yet me know when you strto* patch is ready and I'll do the reverse
transformation in _doprnt.

BTW our current implementation of nan* is non-conforming. The ANSI C99 takes a
char * argument (i.e.: <anything> in NaN(<anything>), but the prototype in
<math.h>. gcc 3.3 generated a warning for nan*.

Having said that, our implementations of nan* are not in the ANSI section.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]