This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] __fpurge(3)

From: Ralf Corsepius <ralf dot corsepius at rtems dot org>
To: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
Cc: newlib at sourceware dot org
Date: Wed, 18 May 2011 09:59:48 +0200
Subject: Re: [PATCH] __fpurge(3)
References: <BANLkTinCYG7R3DFVb95ZGO_HCqkdmfgw+Q@mail.gmail.com> <4DD37256.4080607@rtems.org> <BANLkTimnLX7XYW=rBeGXw21u_AQcGAQ=OA@mail.gmail.com>

On 05/18/2011 09:47 AM, Yaakov (Cygwin/X) wrote:

On Wed, May 18, 2011 at 02:16, Ralf Corsepius wrote:

Generally speaking, I am opposed to furtherly extending newlib with
non-standardized functions like these.

I don't know what others (esp. Cygwin) think about such kind of extensions,
but I'd like to see "not implemented" for RTEMS
(i.e. at minimum #ifndef __rtems__).

Cygwin's homepage makes it pretty clear:

a Linux API layer providing substantial Linux API functionality.


First, stdio/fpurge.c is ELIX_LEVEL_4.  Secondly, why should
__fpurge(3) be any different than fpurge(3)?

History - We don't use neither and will likely want to get rid of fpurge, too.

Ralf

Follow-Ups:
- Re: [PATCH] __fpurge(3)
  - From: Eric Blake

References:
- [PATCH] __fpurge(3)
  - From: Yaakov (Cygwin/X)
- Re: [PATCH] __fpurge(3)
  - From: Ralf Corsepius
- Re: [PATCH] __fpurge(3)
  - From: Yaakov (Cygwin/X)

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