This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: vfscanf in newlib

To: cygwin-developers at cygwin dot com, newlib at sources dot redhat dot com
Subject: Re: vfscanf in newlib
From: Christopher Faylor <cgf at redhat dot com>
Date: Fri, 20 Apr 2001 22:55:39 -0400
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> <20010420152744.A26175@redhat.com> <3AE0E6C9.CFA716BF@ece.gatech.edu> <20010420224935.A4247@redhat.com>
Reply-To: cygwin-developers at cygwin dot com

On Fri, Apr 20, 2001 at 10:49:35PM -0400, Christopher Faylor wrote:
>I just checked and see that there are a few functions defined that way
>now but I'm not sure what the rationale for doing things this way is.

I should have said that there are "a few functions exported that way"
in cygwin.din.

cgf

References:
- Re: vfscanf in newlib
  - From: Charles S. Wilson
- Re: vfscanf in newlib
  - From: Christopher Faylor
- Re: vfscanf in newlib
  - From: Christopher Faylor
- Re: vfscanf in newlib
  - From: Charles Wilson
- Re: vfscanf in newlib
  - From: Christopher Faylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]