Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30820 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82895 invoked by uid 1010); 12 Jul 2007 01:41:55 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 82879 invoked from network); 12 Jul 2007 01:41:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jul 2007 01:41:54 -0000 Authentication-Results: pb1.pair.com header.from=ceo@l-i-e.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ceo@l-i-e.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain l-i-e.com from 67.139.134.202 cause and error) X-PHP-List-Original-Sender: ceo@l-i-e.com X-Host-Fingerprint: 67.139.134.202 o2.hostbaby.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [67.139.134.202] ([67.139.134.202:2004] helo=o2.hostbaby.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 79/5B-05872-1E685964 for ; Wed, 11 Jul 2007 21:41:54 -0400 Received: (qmail 13897 invoked by uid 98); 12 Jul 2007 01:41:56 -0000 Received: from 127.0.0.1 by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-2.01 (clamdscan: 0.88.7/3634. Clear:RC:1(127.0.0.1):. Processed in 0.087715 secs); 12 Jul 2007 01:41:56 -0000 Received: from localhost (HELO l-i-e.com) (127.0.0.1) by localhost with SMTP; 12 Jul 2007 01:41:56 -0000 Received: from 24.1.37.132 (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Wed, 11 Jul 2007 20:41:56 -0500 (CDT) Message-ID: <2237.24.1.37.132.1184204516.squirrel@www.l-i-e.com> In-Reply-To: <200707101906.30925.larry@garfieldtech.com> References: <1181829227.3478.3.camel@localhost.localdomain> <4692B1A3.1000808@zend.com> <4692B7D4.6040001@zend.com> <200707101906.30925.larry@garfieldtech.com> Date: Wed, 11 Jul 2007 20:41:56 -0500 (CDT) To: "Larry Garfield" Cc: internals@lists.php.net Reply-To: ceo@l-i-e.com User-Agent: Hostbaby Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6? From: ceo@l-i-e.com ("Richard Lynch") On Tue, July 10, 2007 7:06 pm, Larry Garfield wrote: > If 90% of the strings in use would work fine if treated as unicode, > then it > would make sense to just always assume Unicode unless explicitly > specified > otherwise. If that 10% includes enough users who have written millions of line of code in a self-consistent manner that voids ALL their work, you may want to re-think this 90% number you have chosen... And of course you need 2 distinct data types for Unicode and strings. What I don't understand is why you'd lock things down so that: a) the default "string" is Unicode, breaking XX% of existing applications b) the end user can't readily change a) in a huge percentage of existing install base (read: non-dedicated hosting or mixed-user servers with shared httpd.conf settings) I realize it's far too late by now to do anything about it, most likely, but why in the world didn't you just choose a new keyword to define/declare a string as Unicode? And did I dream the thread on this way back when where it was stated that Unicode was backwards-compatible, so this wouldn't be a problem? Yet now it seems that UTF-16 is *not* backwards-compatible, and this seems like a pretty big problem to me. Oh well. I guess I'll just shut up and hope most of my code doesn't break when I go copying/pasting it into new sites that are locked into Unicode mode with no way for me to change that... -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?