From: Eric Grosse <ehg@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] double->string conversion
Date: Mon, 29 Oct 2001 17:52:05 -0500 [thread overview]
Message-ID: <20011029225212.6B67E199EC@mail.cse.psu.edu> (raw)
> what parameters does the %g conversion need to ensure
> that a later strtod will produce the same value?
%.17g is enough.
http://plan9.bell-labs.com/netlib/fp/g_fmt.c.gz gives a
shorter string, in general, that also promises to exactly
reproduce the starting binary value.
Eric
next reply other threads:[~2001-10-29 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 22:52 Eric Grosse [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 14:05 rog
2001-10-26 20:45 Eric Grosse
2001-10-26 20:37 rog
2001-10-26 20:27 Russ Cox
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=20011029225212.6B67E199EC@mail.cse.psu.edu \
--to=ehg@research.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).