Re: `>>' can't read what `<<' produced: NaNs and Inf

[Benjamin Kosnik <bkoz@cygnus.com>]

> | not numbers (NaN) or are infinity (Inf).
> | However, `>>' can't read those tokens. Is this deliberate?
> 
> I don't think so. Personnally, I came accross, a few days ago, the
> question of whether libtsdc++ should allow this or not--that was when
> reading LIA-1. A quick look at clause 2 (Lexical conventions) lets me
> under the impression that allowing reading NaN, Inf or so should be
> flagged as extensions.

Gaby, what is LIA-1? Eeeek. I can't find a part of 14882 that deals with
this issue--an oversight? Or am I blind? Does this need to get forwarded
to the library issues list?

> My inclination will be to get it into lidstc++ as an extension. Does
> anyone have another idea ? 

Good idea. I say we either wrap this stuff with a suitable macro from
bits/c++config.h, such as:

// Use corrected code from the committee library group's issues list.
#define _G_RESOLVE_LIB_DEFECTS 1

Or make some other (documented) macro guard to turn on and off this
extension. 

I would like to have this functionality though, in some form. I would also
like to do the relevant reading, so I'd appreciate any pointers. . .

Thanks,
Benjamin