Re: [RFC] UString

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