Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73108
Return-Path: <cryptocompress@googlemail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 39105 invoked from network); 13 Mar 2014 11:28:56 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 13 Mar 2014 11:28:56 -0000
Authentication-Results: pb1.pair.com smtp.mail=cryptocompress@googlemail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=cryptocompress@googlemail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.214.54 as permitted sender)
X-PHP-List-Original-Sender: cryptocompress@googlemail.com
X-Host-Fingerprint: 209.85.214.54 mail-bk0-f54.google.com  
Received: from [209.85.214.54] ([209.85.214.54:39992] helo=mail-bk0-f54.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 7A/94-12560-67691235 for <internals@lists.php.net>; Thu, 13 Mar 2014 06:28:55 -0500
Received: by mail-bk0-f54.google.com with SMTP id 6so65352bkj.41
        for <internals@lists.php.net>; Thu, 13 Mar 2014 04:28:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=IxjW5LzBJ3423c8wXo820iEkjY5aLCJZHgGFrHrKJ84=;
        b=NFZCi/v1tvBzhnczmHTDVGHnq+WtQNKQ7gTRMzvbQOAPlAOWECBfeRYhoUgNky/7nq
         rVsH6sVkxolJwe3zHoQ35HDMB28UNm7Ur6IohBcjP1FdRg0KeXpse2iZIdA1e3UkcgAf
         3WbYgQv3cD1Qqmw5UbtdOQbjU+pvqQuzLTGJ3hoDsEqrs8CFeN2j7h81NAxpeyqZCV06
         uo8lTBcdi9MRh/htvjerDXnJDEofzY22SKoSIcoUSKKCcsQQGZ0O+ygI8AeOHOihXPJb
         VRhTMweW/Jby8krLmCHDFXIUojVpnXGapjntStz+oq+z0soN7De8yVHXstn5J0GCVBuZ
         vNUQ==
X-Received: by 10.205.106.130 with SMTP id du2mr30471bkc.133.1394710131081;
        Thu, 13 Mar 2014 04:28:51 -0700 (PDT)
Received: from [192.168.1.115] (mnch-4d04da03.pool.mediaways.net. [77.4.218.3])
        by mx.google.com with ESMTPSA id r1sm2220011bkk.2.2014.03.13.04.28.48
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Thu, 13 Mar 2014 04:28:49 -0700 (PDT)
Message-ID: <53219669.1020501@googlemail.com>
Date: Thu, 13 Mar 2014 12:28:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Lester Caine <lester@lsces.co.uk>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <531EE602.3090207@lsces.co.uk> <531EEE2A.2000602@googlemail.com> <531F0146.5010701@lsces.co.uk> <53202DC5.4010306@googlemail.com> <532033E1.60602@lsces.co.uk> <53203687.7090405@googlemail.com> <532037F4.6020204@googlemail.com> <CAEZPtU5G41OKb2FQF4ajKgszATqtwxL9E_k4Zc78RZGL8B4qnQ@mail.gmail.com> <532049BB.2080605@lsces.co.uk> <53204C6B.3000506@googlemail.com> <5320511A.7040606@lsces.co.uk> <5320F554.5000109@lerdorf.com> <53210857.5040908@googlemail.com> <CAGa2bXZTfubkyD=nT8fCxzF=P3Y1sPnFgj8nKHDjLB2HiPgFvw@mail.gmail.com> <53216D44.5040802@googlemail.com> <532177CE.4080706@lsces.co.uk>
In-Reply-To: <532177CE.4080706@lsces.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Unicode strings?
From: cryptocompress@googlemail.com (Crypto Compress)

Am 13.03.2014 10:18, schrieb Lester Caine:
> Crypto Compress wrote:
>>> Good point, but users should use NFC UTF-8 without BOM for 
>>> variable/function
>>> names.
>>> It would be documentation issue.
>>
>> in the languages i know combining diacritics are not common so can't 
>> evaluate
>> how practical it is to type those. Would it be impossible to change 
>> code with a
>> dumb editor?
>>
>> $café !== $café
>> 0x63 0x61 0x66 0xC3 0xA9
>> 0x63 0x61 0x66 0x65 0xCC 0x81
>
> 'cryptocompress' (is that really on your passport :( )
>
> This is exactly the area we need to agree on a plan moving forward.
>
> There are a number of options on the table
>
> 1 - Limit variable and other names to 'ASCII' only characters so that 
> case folding can be maintained.
>
> 2 - Remove 'case insensitivity' but not just for point 1 reasons.
> ( I see this as your example being two different strings ;) )
>
> 3 - Allow unicode names to be used in places where they currently 
> cause problems.
>
> Not actually using unicode variable names myself, I still don't 
> understand where the problems are with '3' except for the simple 
> comparison case where normalizing and case conversion creates a 
> minefield? People are currently using unicode in these areas and 
> understand many of the restrictions?
>

My unverified assumption is: The performance impact (cli without 
opcache) is too huge to get this right. If we do not get this right, 
there are complainers. How shall we die?

Виталий