Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58882
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain l-i-e.com designates 67.139.134.202 as permitted sender)
Message-ID: <1d2866192ddfbaaf8710f381794bec12.squirrel@www.l-i-e.com>
In-Reply-To: <4F5D9C77.3030000@lerdorf.com>
References: <4F5D9C77.3030000@lerdorf.com>
Date: Mon, 12 Mar 2012 14:31:32 -0500
To: internals@lists.php.net
User-Agent: SquirrelMail/1.4.21 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] default charset confusion
From: ceo@l-i-e.com ("Richard Lynch")

On Mon, March 12, 2012 1:49 am, Rasmus Lerdorf wrote:
> What we really need is what we added in PHP 6. A runtime encoding ini
> setting that is distinct from the output charset which we can use
> here.

The usual argument against another php.ini setting, other than "too
many already" is the difficulty it presents to write portable code
libraries.

I'm not smart enough to predict how such a setting (regardless of its
name) would help or hinder a library of code that doesn't want another
conditional in a zillion places.

But you folks are that smart. :-)

And I haven't seen any discussion regarding this sub-issue.

So, how would the help / hinder authors of generic library code to be
distributed in the wild?

Forgive me if the answer is so blindingly obvious I should already
know it... :-)

-- 
brain cancer update:
http://richardlynch.blogspot.com/search/label/brain%20tumor
Donate:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE