Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100728
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.194 as permitted sender)
To: Lester Caine <lester@lsces.co.uk>, internals@lists.php.net
References: <da7da5b0-2fc1-b92c-aaa9-b39413b000f7@lsces.co.uk>
 <ec760155-7d65-14e5-8d7c-3008749b0ab9@gmail.com>
 <2307c713-df4a-f27b-602b-86ea740f22a9@lsces.co.uk>
Message-ID: <2acdf58e-b680-e597-d69b-92392375477a@gmail.com>
Date: Wed, 20 Sep 2017 15:19:21 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <2307c713-df4a-f27b-602b-86ea740f22a9@lsces.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Progress or just 'a mess'?
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Having established that the only characters that are case-insensitive in
> PHP7 ... the unicode basic latin set ... the discussion SHOULD be on
> either expanding that to cover all case folding or simply removing this
> rather limited case? 

Why? Does anybody seriously need Russian case folding in PHP constants?
I mean, sure, nice demo, but does anybody *need* it? I don't see much
code on github - in any language - that uses Russian identifiers, for
example.

> argument. However many of my clients do not use English as a first
> language so any data handling has to be unicode based, and case in that

You seem to be mixing data and code here. So what you are talking about
- data or code?
-- 
Stas Malyshev
smalyshev@gmail.com