Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73100
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 18741 invoked from network); 13 Mar 2014 08:33:22 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 13 Mar 2014 08:33:22 -0000
Authentication-Results: pb1.pair.com header.from=cryptocompress@googlemail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=cryptocompress@googlemail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.214.43 as permitted sender)
X-PHP-List-Original-Sender: cryptocompress@googlemail.com
X-Host-Fingerprint: 209.85.214.43 mail-bk0-f43.google.com  
Received: from [209.85.214.43] ([209.85.214.43:52671] helo=mail-bk0-f43.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 08/D0-12560-05D61235 for <internals@lists.php.net>; Thu, 13 Mar 2014 03:33:21 -0500
Received: by mail-bk0-f43.google.com with SMTP id v15so44109bkz.2
        for <internals@lists.php.net>; Thu, 13 Mar 2014 01:33:17 -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:cc:subject
         :references:in-reply-to:content-type;
        bh=Y7NyyYvfEM7srY0Zm4yiVLdrgOxZHsxod6C+PqwVc8Y=;
        b=i+5ja78h+uB6PerealOFQnZj26QIHIybnbXE+Ch+iPfL64wYVP3iFQKOB16Qe/4gAv
         zp/l9v/HkbNSBX7tu1Z5My9uK1cumLLcqbk3lsjNMj7aiHIcXmw7nvJbhPvCciV7UA0H
         jidq6C+6e1tVO2GlaqP2cBlD+Ygb5v/oo+pVPUYVvPRPErbmnfI0JlfdLmkyqcRNQfFP
         pdBbwsNev74A61RLBBmuqXKQjHyGN3kKWsnq0/A9TSl58egVDizibCsk+TlOj8aydGjX
         oEzzPiZLtvjeD6uhfKw/jEmprDb3IKb3X2eOea0Nobb2BUa+OhkIXUUIVlWgUwETJ4j5
         kGfA==
X-Received: by 10.205.99.1 with SMTP id cq1mr294996bkc.5.1394699597409;
        Thu, 13 Mar 2014 01:33:17 -0700 (PDT)
Received: from [192.168.1.115] (mnch-4d04da03.pool.mediaWays.net. [77.4.218.3])
        by mx.google.com with ESMTPSA id bh9sm1706336bkb.16.2014.03.13.01.33.15
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Thu, 13 Mar 2014 01:33:16 -0700 (PDT)
Message-ID: <53216D44.5040802@googlemail.com>
Date: Thu, 13 Mar 2014 09:33:08 +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: Yasuo Ohgaki <yohgaki@ohgaki.net>
CC: 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>
In-Reply-To: <CAGa2bXZTfubkyD=nT8fCxzF=P3Y1sPnFgj8nKHDjLB2HiPgFvw@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------000803020000060901030507"
Subject: Re: [PHP-DEV] Unicode strings?
From: cryptocompress@googlemail.com (Crypto Compress)

--------------000803020000060901030507
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Yasuo,

>         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.
>
>
>     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.

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

--------------000803020000060901030507--