This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: `>>' can't read what `<<' produced: NaNs and Inf
- To: Joao Cardoso <jcardoso@inescn.pt>
- Subject: Re: `>>' can't read what `<<' produced: NaNs and Inf
- From: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
- Date: 30 Mar 1999 22:52:17 +0200
- Cc: libstdc++@sourceware.cygnus.com
- Organization: CMLA, ENS Cachan -- CNRS URA 1611 (France)
- References: <3700FBC4.3C4C5EFB@inescn.pt>
Joao Cardoso <jcardoso@inescn.pt> writes:
| Hi,
|
| [I have recently put a question on the egcs mailing list, but this is
| the correct place to do it, I think.]
|
| `<<' generate special tokens when outputing float/doubles that are
| 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.
|
| If I submit a patch to make libstdc++ read what it output, will it be
| accepted (in principle)? I think that no standard specify it...
If you have a patch, then send it to the list.
My inclination will be to get it into lidstc++ as an extension. Does
anyone have another idea ?
-- Gaby