[Cfp-interest] signaling NaN I/O issue?

[Jim Thomas]

Rajan,

Thanks for the clarification. Functions that don't signal on signaling 
NaN inputs need to return a signaling NaN. Signaling NaNs shouldn't 
quietly go away. Printf can't return a character string representation 
of a signaling NaN, because there isn't one.

-Jim

Rajan Bhakta wrote:

>
> Hi Jim,
>
> I was saying that the fact that given we do not yet require functions 
> to signal when passed in a sNAN, why are we making the stdio family of 
> functions a special case in that they must signal and convert the 
> argument to a qNAN? I don't think that special casing certain library 
> functions is a good idea due to the precedent it would set.
>
> Regards,
>
> Rajan Bhakta
> z/OS XL C/C++ Compiler Technical Architect
> ISO C Standards Representative for Canada
> C Compiler Development
> Contact: rbhakta at ca.ibm.com, Rajan Bhakta/Toronto/IBM
> Telephone: (905) 413-3995
>
>
> From: 	Jim Thomas <jwthomas at cup.hp.com>
> To: 	Rajan Bhakta/Toronto/IBM at IBMCA
> Cc: 	"cfp-interest at ucbtest.org" <cfp-interest at ucbtest.org>
> Date: 	05/05/2011 06:06 PM
> Subject: 	signaling NaN I/O issue?
>
>
> ------------------------------------------------------------------------
>
>
>
> Hi Rajan,
>
> Just before leaving the teleconference this morning you commented on the
> last item in Fred's paper (re 7.21.1). Afterwards we weren't sure we'd
> understood your point. Please clarify.
>
> -Jim
>
>