Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30187 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56432 invoked by uid 1010); 14 Jun 2007 16:03:26 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 56409 invoked from network); 14 Jun 2007 16:03:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jun 2007 16:03:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.183 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.146.183 wa-out-1112.google.com Received: from [209.85.146.183] ([209.85.146.183:43757] helo=wa-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/76-08628-BC661764 for ; Thu, 14 Jun 2007 12:03:24 -0400 Received: by wa-out-1112.google.com with SMTP id l24so741230waf for ; Thu, 14 Jun 2007 09:03:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NjKQQtGg1E2XUkBRh9Vq7jzM2E1LFt4GzhizKXrLkTqmu0IEe2W8BE5GYN35CvzZy9nWY5pPYHVWGCaJNXvW43lyKgMPC3GYCO6DVC+9aS6y7kdJ4NnJbTSahOJuoeWXNTqE+G2lSpY90BTyG2YSQLBaTpxqEtvDjvnHVMkFP70= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Fyud9CMn8oKZB5iEJ6PP+8bve/j938bSFE8Lmhx9OOO3H1eIKbF9UALH0OJE8nXjjhIX0PXPKYjkN62J5olR6lQX36qlZ8XdznkHuBaDwbYJJQNxzKHmD4DAgss9dMhP8LjnG5qZP97NI6eWqno3kJvJfu3xIOVSRw55gU9mj3E= Received: by 10.115.107.1 with SMTP id j1mr2002806wam.1181836997225; Thu, 14 Jun 2007 09:03:17 -0700 (PDT) Received: by 10.114.180.9 with HTTP; Thu, 14 Jun 2007 09:03:17 -0700 (PDT) Message-ID: Date: Thu, 14 Jun 2007 18:03:17 +0200 To: "Rasmus Lerdorf" Cc: jani.taskinen@iki.fi, internals@lists.php.net In-Reply-To: <467161ED.9040300@lerdorf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1181829227.3478.3.camel@localhost.localdomain> <46715887.4010306@lerdorf.com> <467161ED.9040300@lerdorf.com> Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6? From: pierre.php@gmail.com (Pierre) Hi Rasmus, On 6/14/07, Rasmus Lerdorf wrote: > > As a side note, we had the same thoughts about php5, it did not work. > > Not really. Nothing in PHP 5 was designed to break compatibility with > PHP 4. In theory, I agree with you here, we were very careful about BC. However in practice, there was a few troubles which made a smooth migration (like running php4 code directly in php5) a little pain until 5.1. But then the new fatal errors brought other troubles... However my point was about making design choices to minimize the migration momentum. It did not work for PHP5. It worked (I can be wrong, it is too old) well for php3 to php4 because there was really a huge improvement in the core language (begin of "OO" support, even if it was not perfect) and its features in general (extensions). I fear that Unicode is not that appealing for almost all users, even those who actually need it, they already rely on mb_string and other home made solutions. But I tend to be too much realistic/pessimist. --Pierre