[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1811141840140.16571@digraph.polyomino.org.uk>
Date: Wed, 14 Nov 2018 18:47:57 +0000
From: Joseph Myers <joseph@...esourcery.com>
To: Daniel Colascione <dancol@...gle.com>
CC: Szabolcs Nagy <Szabolcs.Nagy@....com>,
Dave P Martin <Dave.Martin@....com>, nd <nd@....com>,
Florian Weimer <fweimer@...hat.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Joel Fernandes <joelaf@...gle.com>,
Linux API <linux-api@...r.kernel.org>,
Willy Tarreau <w@....eu>, Vlastimil Babka <vbabka@...e.cz>,
Carlos O'Donell <carlos@...hat.com>,
"libc-alpha@...rceware.org" <libc-alpha@...rceware.org>
Subject: Re: Official Linux system wrapper library?
On Wed, 14 Nov 2018, Daniel Colascione wrote:
> A good demonstration of a new commitment to pragmatism would be
> merging the trivial wrappers for gettid(2).
I support the addition of gettid (for use with those syscalls that take
tids, and with appropriate documentation explaining the properties of
tids) - and, generally, wrappers for all non-obsolescent
architecture-independent Linux kernel syscalls, including ones that are
very Linux-specific, except maybe for a few interfaces fundamentally
inconsistent with glibc managing TLS etc. - they are, at least, no worse
as a source of APIs than all the old BSD / SVID interfaces we have from
when those were used as sources of APIs.
--
Joseph S. Myers
joseph@...esourcery.com
Powered by blists - more mailing lists