Yes, POSIX locales should not be used either in internal or userland
printf() unless we're using en_US locale.
-Andrei
On Jan 5, 2007, at 6:15 AM, Matt Wilmas wrote:
Hi Andrei,
I have no idea. :-) It doesn't really affect me personally that I can
think
of, so whatever you guys decide. I don't feel strongly either way...
I
just wanted to bring up the internal changes originally after the
locale
stuff created the bug with number_format() (maybe a couple others).
In your first reply (weeks ago), you mentioned POSIX locales being
deprecated in Unicode mode, and I assumed you were referring to the
internal
printf, but maybe you meant PHP's userland printf. Well, whichever
version,
I'm neutral on what to do. Oh, and to clarify that the
locale-awareness
wasn't "a good idea" in my last message, I meant as far as breaking
things
(internal or 3rd party), not just in general...
Matt
----- Original Message -----
From: "Andrei Zmievski"
Sent: Thursday, January 04, 2007
So we should remove locale-awareness then?
-Andrei
On Jan 4, 2007, at 5:15 AM, Matt Wilmas wrote:
Hi Andrei,
No, not really... :-) I agree with what you said. Even in
non-Unicode mode
or 5.2, it doesn't seem like making things locale aware which weren't
before
is a good idea (3rd party code that's relying on behavior, etc.
which I
think was mentioned elsewhere).
Matt
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
