Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15164
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: built-in printf %f parameter format depend on LC_NUMERIC |
| Date | 2019-07-14 13:57 -0400 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.1305.1563127037.2688.bug-bash@gnu.org> (permalink) |
| References | (7 earlier) <a048b783-79c0-24fe-d456-deea9a50a149@case.edu> <51bed6f0-eeb8-c93b-33e7-6ccaf4d73b3f@blastwave.org> <a46a31ec-76b0-ccca-b867-831331413860@case.edu> <87o91zar2p.fsf@igel.home> <fdde7f87-c42e-877c-6023-ea721d7ea8db@case.edu> |
On 7/12/19 5:19 PM, Andreas Schwab wrote: > On Jul 12 2019, Chet Ramey <chet.ramey@case.edu> wrote: > >> I assume this means that bc doesn't use strtod. > > Of course not, strtod doesn't parse arbitrary precision numbers. Yes, exactly. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: built-in printf %f parameter format depend on LC_NUMERIC Chet Ramey <chet.ramey@case.edu> - 2019-07-14 13:57 -0400
csiph-web