This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: vfscanf in newlib
- To: "J. Johnston" <jjohnstn at cygnus dot com>
- Subject: Re: vfscanf in newlib
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Fri, 20 Apr 2001 15:27:44 -0400
- Cc: cygwin-developers at cygwin dot com, "Charles S. Wilson" <cwilson at ece dot gatech dot edu>, newlib at sources dot redhat dot com
- References: <3ADD0441.91F76FB6@ece.gatech.edu> <3ADE1FC1.F0A10A89@cygnus.com> <3ADE640A.34E88DCE@ece.gatech.edu> <3AE040FC.16BD67BC@ece.gatech.edu> <3AE070F3.1C45633A@cygnus.com> <20010420145228.B25768@redhat.com> <3AE0894D.5288FDF3@cygnus.com>
- Reply-To: cygwin-developers at cygwin dot com
On Fri, Apr 20, 2001 at 03:09:01PM -0400, J. Johnston wrote:
>Christopher Faylor wrote:
>>
>> On Fri, Apr 20, 2001 at 01:25:07PM -0400, J. Johnston wrote:
>> >> Since the cygwin folks are about to release a new official kernel (1.3.0
>> >> this weekend) I'd like to get these changes into newlib quickly. Other
>> >> than the tests promised above, what else do I need to do to facilitate
>> >> that?
>> >>
>> >
>> >You should try out the new patch. The new patch adds a few new _r
>> >routines that should also be added to Cygwin which alters the Cygwin
>> >portion of your patch.
>>
>> Chuck,
>> If you can submit the appropriate cygwin changes, I'll definitely get them
>> into 1.3.0.
>>
>
>As discussed, I have attached the new patch. I moved stuff around in stdio.h
>because there were multiple sections using the same #ifdef. There were also
>some routines that were not properly under the non-strict ANSI flag.
I'm not sure if this is directed to me, but I was just asking Chuck for the
appropriate cygwin.din changes.
I decided that it was silly for me to ask him to do this since it is easy to
do myself, though, so I've made the appropriate modifications. So, if/when you
check this in we'll be ready.
cgf