[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130211134454.GR20323@brightrain.aerifal.cx>
Date: Mon, 11 Feb 2013 08:44:54 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: [PATCH 2/3] Have different definitions of
__pthread_tsd_main agree in size
On Mon, Feb 11, 2013 at 02:38:08PM +0100, Jens Gustedt wrote:
> > there are posix requirements for environ so it must be weak
> > i'm not sure about the alias though
>
> Anyhow the use of environ versus __environ was just not consistent
> through the rest of musl. I have send another patch that should heal
> that.
The current intended usage is that __environ is used in ISO C
functions and startup code that must not reference the name environ
(since it's in the namespace reserved for the application), and POSIX
and extension functions use environ. There's no reason the latter
_need_ to use environ though; it was just more convenient and less
implementation-specific. If you think there's a good reason to change
it after reading this, let's discuss it.
Rich
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.
