Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30281 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70847 invoked by uid 1010); 20 Jun 2007 11:15:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 70831 invoked from network); 20 Jun 2007 11:15:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jun 2007 11:15:50 -0000 Authentication-Results: pb1.pair.com header.from=jani.taskinen@sci.fi; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=jani.taskinen@sci.fi; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.171 cause and error) X-PHP-List-Original-Sender: jani.taskinen@sci.fi X-Host-Fingerprint: 63.208.196.171 outbound.mailhop.org FreeBSD 4.6-4.9 Received: from [63.208.196.171] ([63.208.196.171:1476] helo=outbound.mailhop.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 19/F4-13585-36C09764 for ; Wed, 20 Jun 2007 07:15:49 -0400 Received: from cs136054.pp.htv.fi ([213.243.136.54] helo=[192.168.1.100]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1I0yA5-00009M-3c; Wed, 20 Jun 2007 07:15:45 -0400 X-MHO-User: U2FsdGVkX19GHdgfPRojiwtBIAZo0hMlDH2kjFh4Xso= X-MHO-User: U2FsdGVkX1/w/OYRh0CYDIm/leglIzEni75dfE9Wjn8= X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 213.243.136.54 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+4qVlEXw8qBwASlWGaLXLOKYSvek5IkFA= Message-ID: <46790C60.6020300@sci.fi> Date: Wed, 20 Jun 2007 14:15:44 +0300 Reply-To: jani.taskinen@iki.fi User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Rasmus Lerdorf CC: Ilia Alshanetsky , internals@lists.php.net 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> <21277473-1502-4F7E-9C3B-BE42C50DD7CB@prohost.org> <467839D0.2020301@lerdorf.com> In-Reply-To: <467839D0.2020301@lerdorf.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6? From: jani.taskinen@sci.fi (Jani Taskinen) What I think Ilia said (between the lines) is that basically we're forking PHP. Perhaps we really need to accept the fact that this has already happened.. It started with the CPR for PHP_4_4 branch and same is now continuing with the PHP_5_2 branch. If the support for PHP 4 was _officially_ dropped by release of PHP 5, the adoption of PHP 5 would have been quicker than it has been so far. --Jani Rasmus Lerdorf kirjoitti: > Ilia Alshanetsky wrote: >> Sorry to interject, but just a quick slighty off topic note. >> >> In your earlier e-mail you've said that >> >> ----------------- >> >> I actually don't have a problem with 95% of PHP 6 installations turning >> off Unicode support and this being the default setting for ISP's. >> >> Full Unicode support in an application is a big commitment and it will >> take quite a bit of work. I just don't think that many people will >> invest the time and effort into doing this, but at the same time there >> will be large applications and services that have full control over >> their server settings that will make use of it. Think Flickr, Yahoo, >> Facebook, etc. >> >> ----------------- >> >> Since 95% of installations will not be using PHP6 (php6 without unicode >> is pretty much a slower version php5) for whatever reason, >> we need a common version for the other 95%. I think it is inevitable >> that there will be 2 continually developed versions of PHP out there, >> one for people who need unicode support in the way that is envisioned by >> PHP6 and one for people who don't need it. > > Well, PHP is going to evolve and get more features and performance > enhancements. Those are all going to go into PHP 6 and above. People > stuck on PHP 5 won't see any of these, so I don't see PHP 6 without > unicode as just a slower version of PHP 5. Namespaces and some of the > other PHP 6 planned features are probably quite interesting to a number > of people some of whom may not be interested in Unicode. > > -Rasmus >