Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78217
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
User-Agent: K-9 Mail for Android
In-Reply-To: <2EAD2B07-1469-440B-9843-BB1D5CD56E68@ajf.me>
References: <1413875212.2624.3.camel@localhost.localdomain> <5446C552.2080702@gmail.com> <2EAD2B07-1469-440B-9843-BB1D5CD56E68@ajf.me>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Wed, 22 Oct 2014 08:46:52 +0100
To: Andrea Faulds <ajf@ajf.me>
CC: internals@lists.php.net
Message-ID: <084F0AF2-20AC-4F51-B8C2-C8695B0C8530@gmail.com>
Subject: Re: [PHP-DEV] [RFC] UString
From: rowan.collins@gmail.com (Rowan Collins)

On 21 October 2014 23:21:37 GMT+01:00, Andrea Faulds <ajf@ajf.me> wrote:
>
>> On 21 Oct 2014, at 21:42, Rowan Collins <rowan.collins@gmail.com>
>wrote:
>> 
>> The only case I can see where a default encoding would be sensible
>would be where source code itself is in a different encoding, so that
>u('literal string') works as expected.
>
>This is only a good idea if we can somehow make it file-local.
>Otherwise if one library uses Latin-1 and another uses UTF-8 for some
>reason, bang!

Yes, I used the word "declared" advisedly, because I was thinking it could take its default encoding (if we were to go down the route of special literal syntax rather than wrapper-function) from the existing declare(encoding='...') directive, rather than a global variable or setting.

http://php.net/manual/en/control-structures.declare.php#control-structures.declare.encoding