Re: [PATCH] Fix newly exposed bug [was RE: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]]

2005-04-29 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Dave Korn on 4/28/2005 12:41 PM: Heh, actually we probably have to talk about that. The k should IIUIC be swallowed by the %lf and the %c should fail; this is the production described as NAN(n-char-sequence opt) in the C language

[PATCH] Fix newly exposed bug [was RE: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]]

2005-04-28 Thread Dave Korn
Original Message From: Jean-Christophe Kablitz Sent: 27 April 2005 00:22 Hello, I have noticed, that, while parsing {a float_value immediately followed by 'n' or 'N'} with the %f%c format, the sscanf function of cygwin-1.5.16-1 behaves differently from the scanf function of

Re: [PATCH] Fix newly exposed bug [was RE: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]]

2005-04-28 Thread Jeff Johnston
Hi Dave, Thanks for looking into this. Your patch wasn't quite correct. It ended up breaking nan-support which isn't tested in the accompanying testcase. It needed to verify that x multiple_flags_ored_together == multiple_flags_ored_together. Anyway, I have checked a patch in and

RE: [PATCH] Fix newly exposed bug [was RE: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]]

2005-04-28 Thread Dave Korn
Original Message From: Jeff Johnston Sent: 28 April 2005 19:33 Hi Dave, Thanks for looking into this. Your patch wasn't quite correct. It ended up breaking nan-support which isn't tested in the accompanying testcase. It needed to verify that x multiple_flags_ored_together ==

RE: [PATCH] Fix newly exposed bug [was RE: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]]

2005-04-28 Thread Gary R. Van Sickle
Heh, actually we probably have to talk about that. The k should IIUIC be swallowed by the %lf and the %c should fail; this is the production described as NAN(n-char-sequence opt) in the C language spec, strtod documentation (that's 7.20.1.3.3 in WG14/N843 draft, I don't have the final

RE: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]

2005-04-27 Thread Dave Korn
Original Message From: Jean-Christophe Kablitz Sent: 27 April 2005 00:22 Maybe I have been misusing sscanf. Or there is a relationship with the NaN-parsing problem of the newlib. Best regards. Jean-Christophe K. Almost certainly so; thanks for the test case, I'll get onto it

Re: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]

2005-04-26 Thread Jean-Christophe Kablitz
- From: Jeff Johnston jjohnstn at redhat dot com To: Dave Korn dave dot korn at artimi dot com Cc: cygwin at cygwin dot com; newlib at sources dot redhat dot com Sent: Tuesday, April 05, 2005 8:47 PM Subject: Re: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem] Patch checked in. Thanks

Re: RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]

2005-04-05 Thread Jeff Johnston
Patch checked in. Thanks. -- Jeff J. Dave Korn wrote: Original Message From: Dave Korn Sent: 04 April 2005 19:07 Original Message From: Dave Korn Sent: 04 April 2005 18:51 Original Message From: Michael Hines Sent: 04 April 2005 19:43 The following program prints i=1

RFC: Fix partial NaN-parsing problem [was RE: sscanf problem]

2005-04-04 Thread Dave Korn
Original Message From: Dave Korn Sent: 04 April 2005 19:07 Original Message From: Dave Korn Sent: 04 April 2005 18:51 Original Message From: Michael Hines Sent: 04 April 2005 19:43 The following program prints i=1 x=0 instead of i=0 x=10 when using the