[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87va4zaeai.fsf@oldenburg.str.redhat.com>
Date: Wed, 14 Nov 2018 16:07:17 +0100
From: Florian Weimer <fweimer@...hat.com>
To: Andy Lutomirski <luto@...capital.net>
Cc: Szabolcs Nagy <Szabolcs.Nagy@....com>,
Dave P Martin <Dave.Martin@....com>,
Daniel Colascione <dancol@...gle.com>, nd <nd@....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\@sourceware.org" <libc-alpha@...rceware.org>
Subject: Re: Official Linux system wrapper library?
* Andy Lutomirski:
> Thread cancellation is a big mess, and we only really need to support
> it because on legacy code. The whole mechanism should IMO be
> considered extremely deprecated.
The part regarding legacy code is not true: people write new code using
it all the time. It's true that this feature is difficult to use, and
it is often employed in cases where it is not needed or
counterproductive. However, there are cases where code becomes simpler.
Thanks,
Florian
Powered by blists - more mailing lists