Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18829 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61110 invoked by uid 1010); 13 Sep 2005 13:26:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 61095 invoked from network); 13 Sep 2005 13:26:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Sep 2005 13:26:04 -0000 X-Host-Fingerprint: 204.11.219.139 lerdorf.com Linux 2.4/2.6 Received: from ([204.11.219.139:60273] helo=colo.lerdorf.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id D4/06-58045-B63D6234 for ; Tue, 13 Sep 2005 09:26:03 -0400 Received: from [192.168.2.102] (CPE00131063dcac-CM0011aec551ea.cpe.net.cable.rogers.com [65.49.170.67]) (authenticated bits=0) by colo.lerdorf.com (8.13.4/8.13.4/Debian-4) with ESMTP id j8DDPr8i003974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 13 Sep 2005 06:25:57 -0700 Message-ID: <4326D361.9040200@lerdorf.com> Date: Tue, 13 Sep 2005 09:25:53 -0400 User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ilia Alshanetsky CC: pierre.php@gmail.com, internals References: <4326D0C8.8080509@prohost.org> In-Reply-To: <4326D0C8.8080509@prohost.org> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] PHP6, Unicode for language functions, classes, methods, vars names From: rasmus@lerdorf.com (Rasmus Lerdorf) Ilia Alshanetsky wrote: > Pierre Joye wrote: > >>is not something I like to see. For language constructs, I would >>really like to have only ASCII support... > > > +1 IMHO language identifiers should be limited to ASCII. Yes you can now > use language specific chars by changing the locale, so that ž, č, ÿ are > taken, but that hardly makes for portable code. What do you mean? Why wouldn't it be portable? Because you can't read it? It will still run. Limiting identifiers to ASCII is an artificial limitation as far as I am concerned. I see no reason for it. It's not as if people are going to suddenly write code for distribution with all sorts of weird unicode identifiers. We support high-ascii today and you never see those in public code. Java has had unicode identifiers forever as well, and it doesn't seem to be a problem for them. For people writing localized code it is very nice to be able to use descriptive identifiers in their own character set. It makes it much easier to understand the code for them. -Rasmus