From: Heavenly Avenger <avenger@avenger.ws>
To: cygwin@cygwin.com
Subject: Re: strtod ("nan") returns negative NaN
Date: Tue, 14 Aug 2018 17:08:00 -0000 [thread overview]
Message-ID: <c351c1c2-dac0-b4c4-b640-a749ec3254fa@avenger.ws> (raw)
In-Reply-To: <20180814153528.GY3747@calimero.vinschen.de>
Well, that's what I get in linux and cygwin for:
#include <stdio.h>
#include <stdlib.h>
#include <math.h> /* the last two printfs requires this */
int main (void) {
 printf ("strtof (\"nan\", NULL) = %f\n", strtof ("nan", NULL));
 printf ("strtof (\"-nan\", NULL) = %f\n", strtof ("-nan", NULL));
 printf ("strtod (\"nan\", NULL) = %f\n", strtod ("nan", NULL));
 printf ("strtod (\"-nan\", NULL) = %f\n", strtod ("-nan", NULL));
 printf ("strtold (\"nan\", NULL) = %Lf\n", strtold ("nan", NULL));
 printf ("strtold (\"-nan\", NULL) = %Lf\n", strtold ("-nan", NULL));
 printf ("nan (\"\") = %f\n", nan (""));
 printf ("-nan (\"\") = %f\n", -nan (""));
}
I get:
Gentoo Linux (native linux)
strtof ("nan", NULL) = nan
strtof ("-nan", NULL) = nan
strtod ("nan", NULL) = nan
strtod ("-nan", NULL) = nan
strtold ("nan", NULL) = nan
strtold ("-nan", NULL) = nan
nan ("") = nan
-nan ("") = -nan
cygwin 2.10.0:
strtof ("nan", NULL) = nan
strtof ("-nan", NULL) = nan
strtod ("nan", NULL) = -nan
strtod ("-nan", NULL) = nan
strtold ("nan", NULL) = -nan
strtold ("-nan", NULL) = -nan
nan ("") = nan
-nan ("") = -nan
So, let's hope the patch does not transform the behavior from the nan
from math.h.
And yes, you have a good point. Just, well, different people made those
different parts of the code so, better cygwin follow the ""convention"",
if we can call it, that. :)
On 8/14/2018 12:35 PM, Corinna Vinschen wrote:
> printf ("nan (\"\") = %f\n", nan (""));
> printf ("-nan (\"\") = %f\n", -nan (""));
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-08-14 16:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 15:16 `std::stod ("nan")` " Masamichi Hosoda
2018-08-13 16:53 ` Stephen John Smoogen
2018-08-13 23:46 ` Duncan Roe
2018-08-14 0:46 ` Stephen John Smoogen
2018-08-14 1:10 ` Masamichi Hosoda
2018-08-14 2:31 ` strtod ("nan") returns negative NaN (was `std::stod ("nan")` returns negative NaN) Masamichi Hosoda
2018-08-14 3:25 ` strtod ("nan") returns negative NaN Steven Penny
2018-08-14 4:46 ` Masamichi Hosoda
2018-08-14 9:56 ` Corinna Vinschen
2018-08-14 10:39 ` Corinna Vinschen
2018-08-14 12:18 ` Masamichi Hosoda
2018-08-14 13:23 ` Corinna Vinschen
2018-08-14 13:41 ` Stephen John Smoogen
2018-08-14 15:25 ` Heavenly Avenger
2018-08-14 15:54 ` Corinna Vinschen
2018-08-14 17:08 ` Heavenly Avenger [this message]
2018-08-14 16:05 ` Masamichi Hosoda
2018-08-14 19:24 ` Steven Penny
2018-08-14 21:45 ` Andy Moreton
2018-08-14 22:23 ` Stephen John Smoogen
2018-08-15 0:02 ` Eric Blake
2018-08-15 7:36 ` Steven Penny
2018-08-21 3:18 ` Brian Inglis
2018-08-14 19:44 ` Achim Gratz
2018-08-21 13:28 ` Brian Inglis
2018-08-14 15:05 ` Masamichi Hosoda
2018-08-14 15:21 ` Masamichi Hosoda
2018-08-14 15:35 ` Heavenly Avenger
2018-08-14 20:05 ` Joseph Myers
2018-08-14 20:19 ` Joseph Myers
2018-08-15 8:51 ` Masamichi Hosoda
2018-08-15 12:55 ` Masamichi Hosoda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c351c1c2-dac0-b4c4-b640-a749ec3254fa@avenger.ws \
--to=avenger@avenger.ws \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).