Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73092 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92827 invoked from network); 13 Mar 2014 01:22:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Mar 2014 01:22:44 -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.46 as permitted sender) X-PHP-List-Original-Sender: cryptocompress@googlemail.com X-Host-Fingerprint: 209.85.214.46 mail-bk0-f46.google.com Received: from [209.85.214.46] ([209.85.214.46:62525] helo=mail-bk0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DE/91-17655-26801235 for ; Wed, 12 Mar 2014 20:22:42 -0500 Received: by mail-bk0-f46.google.com with SMTP id v15so23568bkz.33 for ; Wed, 12 Mar 2014 18:22:39 -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=pcS2/w/j4WSCdeNrC11cyXWDxyrRCiuktRHLKDyhRfs=; b=N4jcZQiBhLrWHIkwOX+8zLV8LSdKCY/iewU+fA7YiL9fZXVHjDNpGfcvozR0r5fcdB XuMt7/ypFYGlqj0ctsBNXCyl4HElrikmSaDzcQZh2XQGjlkUzg4Iwn0LPampitIrulHM tArhdwMYdugEFSVRd1czLwcnwfNqcwWYz2C80YkEuLvqXP8tUgZkwcDyPyWOYIsfUNZ/ FiNfoVKSyGG7EkTQOmf2/rnw98iGGrmtDtqyfC6lV513kPfQb42zpLx+S87ZyKwCHbRF Nsm4HgaFMKvopFbijthZhrOeDWc/aTquuBXZ32DeBh9Dn8i+VBuGueStx68iDHDyWM90 4YyA== X-Received: by 10.204.174.17 with SMTP id r17mr629578bkz.23.1394673759351; Wed, 12 Mar 2014 18:22:39 -0700 (PDT) Received: from [192.168.1.115] (mnch-5d854468.pool.mediaWays.net. [93.133.68.104]) by mx.google.com with ESMTPSA id oa10sm824090bkb.14.2014.03.12.18.22.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Mar 2014 18:22:38 -0700 (PDT) Message-ID: <53210857.5040908@googlemail.com> Date: Thu, 13 Mar 2014 02:22:31 +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: PHP Developers Mailing List 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> <532049BB.2080605@lsces.co.uk> <53204C6B.3000506@googlemail.com> <5320511A.7040606@lsces.co.uk> <5320F554.5000109@lerdorf.com> In-Reply-To: <5320F554.5000109@lerdorf.com> 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 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 ; , { } ( ) 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)