Date: Tue, 18 Mar 2003 13:13:44 +0200
From: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <7458-Tue18Mar2003131344+0200-eliz@elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <200303180839.JAA03639@lws256.lu.erisoft.se> (message from Martin
	Stromberg on Tue, 18 Mar 2003 09:39:15 +0100 (MET))
Subject: Re: strto{d,f,ld}, inf and nan patch
References:  <200303180839 DOT JAA03639 AT lws256 DOT lu DOT erisoft DOT se>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: Martin Stromberg <Martin DOT Stromberg AT epl DOT ericsson DOT se>
> Date: Tue, 18 Mar 2003 09:39:15 +0100 (MET)
> 
> Eli said:
> > I think we should at least verify that <anything> is a hex number.
> 
> Nope. Or at least probably not. Because the highest hex number we can
> read is an unsigned long long. That covers the mantissa of a long
> double. Where should the sign bit be indicated?

I was thinking about float and double Inf/NaN, not a long double
Inf/NaN.  Do we agree that what I proposed is feasible for floats and
doubles?

As for the long double, I don't know what should we do.  What does
glibc do, for example?