Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <467BE38C.5040207@roguewave.com>
Date: Fri, 22 Jun 2007 08:58:20 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: STDCXX examples fails and reasons [MSVC]
References: <7BDB2168BEAEF14C98F1901FD2DE64389D67D6@epmsa009.minsk.epam.com>
 <467ABBBA.9030305@roguewave.com>
 <7BDB2168BEAEF14C98F1901FD2DE64389D68F3@epmsa009.minsk.epam.com>
In-Reply-To: <7BDB2168BEAEF14C98F1901FD2DE64389D68F3@epmsa009.minsk.epam.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Farid Zaripov wrote:
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com] 
>> Sent: Thursday, June 21, 2007 8:56 PM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: Re: STDCXX examples fails and reasons [MSVC]
>  
> [...]
> 
>> limits.cpp should produce the qnan for Quiet NAN and snan for
>> Signaling NAN on all platforms.
> 
>   I can't find this requirement in standard.

It's not in the C++ standard but it is in C99, under fprintf(),
the f and F conversion specifier:

     A double argument representing an infinity is converted
     in one of the styles [-]inf or [-]infinity � which style
     is implementation-defined. A double argument representing
     a NaN is converted in one of the styles [-]nan or
     [-]nan(n-char-sequence) � which style, and the meaning
     of any n-char-sequence, is implementation-defined. The
     F conversion specifier produces INF, INFINITY, or NAN
     instead of inf, infinity, or nan, respectively.

Martin