Dear list,
On Thu, 31 Oct 2013 14:19:29 +0000 (UTC) Dima Pasechnik <dimp...@gmail.com> wrote: > On 2013-10-30, Erik Massop <e.mas...@hccnet.nl> wrote: > > This seems to be the bug 'scanf %f doesn't parse "0e+0" correctly' in > > glibc [1]. > > is it really a bug? I am not sure. Normally one should > have used %g format to read in a float in its "natural" > format. There mustn't be a '+' in a fixed-point notation, AFAIK. The (draft of the) C-standard specifies that a,e,f,g all match "an optionally signed floating-point number, infinity or NaN, whose format is the same as expected for the subject sequence of the strtod function." [1, page 319] Hence which of f and g is used should not matter. I guess the behavior might be different in older C versions. Either way, this issue with ATLAS should be gone with glibc 2.19 [2]. Regards, Erik Massop [1] http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1539.pdf [2] https://sourceware.org/bugzilla/show_bug.cgi?id=15917 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
