From: Kbwms AT aol DOT com
Message-ID: <58ca22ce.36a4c038@aol.com>
Date: Tue, 19 Jan 1999 12:26:16 EST
To: moshier AT mediaone DOT net
Cc: Robert Hoehne <robert DOT hoehne AT gmx DOT net>, djgpp-workers AT delorie DOT com
Mime-Version: 1.0
Subject: Re: Bug when printing long doubles
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 38
Reply-To: djgpp-workers AT delorie DOT com

Dear Steve,

On 01-19-99 at 11:32:01 EST you wrote:
>
>
> > Are you saying that you think such numbers should print as "NaN"?
>
> I don't know about "should."   I would favor printing the thing in
> hex or binary and let the user figure out what it means.
>

I see nothing wrong with printing an item of poorly formed bits as NaN.
In the final analysis, that's what it is, isn't it?  When a print loop
inadvertently wades through ASCII or binary data, what's to be done?
In my view, *some* analysis must be done by the person presumably in
charge.

Are there any words in any of the Standards that provide guidance here?
Is this problem limited to poorly-formed long doubles?

K.B. Williams