On Sat, Apr 28, 2001 at 12:46:18AM -0400, Charles S. Wilson wrote:
>Christopher Faylor wrote:
>> How about
>>
>> Subject: What gives with scanf in cygwin 1.31?
>>
>> That has a nice ring to it and I'm sure that the repetition will serve
>> to motivate someone.
>
>sarcasm aside, I don't think its necessary. I rebuilt a debuggable
>kernel from current CVS (of both winsup and newlib) and the scanf()
>functions work. Well, okay, I only explicitly tested vsscanf(), but
>that should cover them all since __svfscanf_r() is used by all *scanf()
>functions. I didn't single-step the new version in gdb, 'cause it
>worked okay (why "debug" a working routine?)
>
>The question is: how did this problem happen? I dunno -- chalk it up to
>a thinko. I tested my changes -- but didn't explicitly test stuff that
>I *knew* was already working -- like the %f scanning in the core routine
>called by all *scanf() functions. Somehow, though, between my changes,
>Jeff's changes, etc. %f parsing got broken. But it seems fixed now.
Didn't Jeff's newlib changes just fix this?
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
