This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Principles for syscall wrappers, again
- From: Rich Felker <dalias at libc dot org>
- To: libc-alpha at sourceware dot org
- Date: Wed, 27 May 2015 10:10:06 -0400
- Subject: Re: Principles for syscall wrappers, again
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 10 dot 1505182114090 dot 16300 at digraph dot polyomino dot org dot uk> <20150519000918 dot GB17573 at brightrain dot aerifal dot cx> <1432630525 dot 3077 dot 36 dot camel at triegel dot csb> <20150526151000 dot GA17573 at brightrain dot aerifal dot cx> <mvmbnh78hly dot fsf at hawking dot suse dot de> <20150526155258 dot GC17573 at brightrain dot aerifal dot cx> <mvm382i8mm6 dot fsf at hawking dot suse dot de>
On Wed, May 27, 2015 at 10:12:49AM +0200, Andreas Schwab wrote:
> Rich Felker <dalias@libc.org> writes:
>
> > That may be how it's used internally in glibc, but not elsewhere.
>
> Of course, since the API doesn't exist yet.
>
> > And that API lacks important things like the private/shared
> > distinction and features beyond basic wait/wake..
>
> Use your imagination.
Sorry, I guess I wasn't clear; my point was just that inventing a new
API has lots of requirements that might not be apparent at first, and
that could easily be overlooked, whereas using the existing API is
guaranteed not to be a regression.
Rich