Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85661
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.215.45 cause and error)
MIME-Version: 1.0
In-Reply-To: <551C3FC4.9050109@gmail.com>
References: <CA+kxMuSvxRq-AvjQSBUc-FiYdTrD_1X2SuQtjWRjTwAbcwWRoA@mail.gmail.com>
	<551C3FC4.9050109@gmail.com>
Date: Wed, 1 Apr 2015 19:28:30 +0000
Message-ID: <CA+kxMuSn7qzjY821d9v3WAK-xgS4Pwi8LGR5v0FLEtDdgYyABw@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Deprecate setlocale?
From: danack@basereality.com (Dan Ackroyd)

On 1 April 2015 at 18:58, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> Hi!

Stanislav Malyshev wrote:
> Library should not assume it runs in C locale,

Because it is not thread-safe, it is not safe for libraries to alter the locale.

I can't see any workaround to make this 'just work' - when printf
cannot be relied on to work in a particular way, there is nothing the
library could do to run safely.

The only sensible thing a library could do in a non-C locale is to not
run.....but as setlocale is not thread safe, that is not possible to
detect correctly.

> I don't think we should remove it. I do think we should warn people that
> in this day and age, setlocale() is very bad way of doing
> internationalization except for very specific cases when you know what
> you are doing.

Is there anything we can do that makes people more aware of it's side
effects, other than to make the warning larger on the manual page?

cheers
Dan