Re: Unicode strings?

From: Date: Thu, 13 Mar 2014 01:53:36 +0000
Subject: Re: Unicode strings?
References: 1 2 3 4 5 6 7 8 9 10 11 12 13  Groups: php.internals 
Request: Send a blank email to internals+get-73095@lists.php.net to get a copy of this message
Hi all, On Thu, Mar 13, 2014 at 10:22 AM, Crypto Compress < cryptocompress@googlemail.com> wrote: > Am 13.03.2014 01:01, schrieb Rasmus Lerdorf: > > On 3/12/14, 5:20 AM, Lester Caine wrote: >> >>> Crypto Compress wrote: >>> >>>> Unicode variable names ARE secondary, but if the handling of unicode >>>>> works as >>>>> well as it seems to be for me then it may be an option that can be >>>>> considered. >>>>> >>>> http://3v4l.org/kWb0U >>>> Please help me, what is this about? >>>> >>> Exactly what has already been discussed? >>> You can use unicode strings in many areas of PHP, but it is not by >>> design, but rather as the result of 'holes' in the design. >>> >> That's not a hole in the design. It was quite deliberate and it had >> little to do with Unicode at the time. It was a deliberate effort to not >> artificially limit identifiers beyond that which the language syntax >> naturally prevented. Think <space> ; , { } ( ) etc. >> >> -Rasmus >> > > IMHO it was the right decision to no artificially limit identifiers and it > is a fair trade-off for case-insensitivity without unicode (class ß{} class > SS{}). > With unicode identifiers there is at least one more problem through > normalization to consider. somewhat simplified: $☀☁ and $⛅ (=== in unicode) > Good point, but users should use NFC UTF-8 without BOM for variable/function names. It would be documentation issue. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net

« previous php.internals (#73095) next »