This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v2] Remove union wait
- From: Florian Weimer <fweimer at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: Andreas Schwab <schwab at suse dot de>, "Carlos O'Donell" <carlos at redhat dot com>, libc-alpha at sourceware dot org
- Date: Tue, 12 Apr 2016 21:20:26 +0200
- Subject: Re: [PATCH v2] Remove union wait
- Authentication-results: sourceware.org; auth=none
- References: <56BE07C8 dot 40205 at redhat dot com> <20160307225511 dot 093E92C3BF5 at topped-with-meat dot com> <56DEA20E dot 3040907 at redhat dot com> <56FBBCAF dot 7090806 at redhat dot com> <20160330223228 dot 6A7382C3C54 at topped-with-meat dot com> <56FC5A6C dot 8090408 at redhat dot com> <mvmy48z5dc2 dot fsf at hawking dot suse dot de> <5707AA6C dot 1080800 at redhat dot com> <mvmegacwm33 dot fsf at hawking dot suse dot de> <570BC36A dot 1050603 at redhat dot com> <20160411215550 dot 692942C3AC8 at topped-with-meat dot com> <570CDE15 dot 2020605 at redhat dot com> <20160412180147 dot EF49C2C39F7 at topped-with-meat dot com>
On 04/12/2016 08:01 PM, Roland McGrath wrote:
I don't dispute those notions as likely realities in many situations.
I just dispute the notion that they are universal absolutes that mean
the middle way is clearly useless to everyone and can be disregarded
out of hand.
Absolutely true in general. Based on available data, I just don't think
staged deprecation is the best approach for dealing with union wait.
Another oddity: Portable software already has a check for the
availability of union wait. A deprecated union wait type will still
pass the configure test, and cause deprecation warnings (possibly
treated as errors) later in the build. Direct removal does not.