Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30351 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72544 invoked by uid 1010); 28 Jun 2007 20:54:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 72529 invoked from network); 28 Jun 2007 20:54:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jun 2007 20:54:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=ceo@l-i-e.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=ceo@l-i-e.com; 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:2215] helo=o2.hostbaby.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 16/F3-21924-81024864 for ; Thu, 28 Jun 2007 16:54:48 -0400 Received: (qmail 35434 invoked by uid 98); 28 Jun 2007 20:54:49 -0000 Received: from 127.0.0.1 by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-2.01 (clamdscan: 0.88.7/3545. Clear:RC:1(127.0.0.1):. Processed in 0.08465 secs); 28 Jun 2007 20:54:49 -0000 Received: from localhost (HELO l-i-e.com) (127.0.0.1) by localhost with SMTP; 28 Jun 2007 20:54:48 -0000 Received: from 216.230.84.67 (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Thu, 28 Jun 2007 15:54:48 -0500 (CDT) Message-ID: <34654.216.230.84.67.1183064088.squirrel@www.l-i-e.com> In-Reply-To: <46783212.4020900@lerdorf.com> References: <1181829227.3478.3.camel@localhost.localdomain> <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com> <4671F184.2020401@lerdorf.com> <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com> <4677E7B1.2080305@lerdorf.com> <4677F5FB.1070206@lerdorf.com> <4678252F.2050803@sci.fi> <46783212.4020900@lerdorf.com> Date: Thu, 28 Jun 2007 15:54:48 -0500 (CDT) To: "Rasmus Lerdorf" Cc: jani.taskinen@iki.fi, 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, June 19, 2007 2:44 pm, Rasmus Lerdorf wrote: > It comes down to predicting the future. Whichever way we go, the > decision is going to be second-guessed. If we have critical mass for > a > clean BC break, then I am ok with it. For me personally it would make > things a bit easier, but I think it would be a long long time before > we > saw any large hosts out there switch to a PHP 6 that can't run common > PHP 5 apps. If they switch to 6 with unicode off, and never ever get around to turning unicode on, will it really be any better? They'll just be running some weird-o setup that causes all kinds of bugs and issues and you'll have users with php 6 apps that won't work in php 6 and who submit bogus bug reports about it, because of the setting. A clean break is probably better, especially if it makes php 6 much more maintainable. Large-scale hosts won't switch to 6 any faster than they switched to 5, unless there are ZERO BC breaks. And nobody can guarantee zero breaks, because there are always buglets. The effort to have unicode off in 6 is probably larger than the effort to document what needs to be done to a PHP 5 app to make it be 6-friendly, or even write tools to auto-convert the buik of a script. If unicode semantics are "on" what exactly is borked in PHP 5? Can that be fixed to be BC without resorting to this toggle? -- 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?