[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210928123902.GB4428@brightrain.aerifal.cx>
Date: Tue, 28 Sep 2021 08:39:02 -0400
From: Rich Felker <dalias@...c.org>
To: Quentin Rameau <quinq@...th.space>
Cc: musl@...ts.openwall.com
Subject: Re: Promoting extension functions up from _GNU_SOURCE ?
On Tue, Sep 28, 2021 at 07:20:05AM +0200, Quentin Rameau wrote:
> Hi Rich,
>
> > For the ones that are POSIX-future, we could go ahead and move them to
> > baseline _POSIX_C_SOURCE, or wait a bit.
>
> What's baseline? Is that 200809L?
Yes.
> Those POSIX-next functions shouldn't be exposed under 200809L anyway,
> but under 202XXXL (whatever is decided at release), should they?
The only officially-supported is "latest". Up til now that's meant
2008 (+TCs) only, but my original intent was always that it be moving
with the standard. We generally don't have different version handling
unless there were interfaces *removed* in the new version (like
gethostby* etc.), which are still exposed under the old version.
If there's a reason this doesn't make sense in the future, it can be
reviewed. But if multiple versions are to be 'supported' in any
nontrivial sense (even complex header logic) there should be
compelling reasons to believe just having the new versions would break
things, not just a box-checking exercise.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
