Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30255 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18591 invoked by uid 1010); 19 Jun 2007 15:09:27 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 18512 invoked from network); 19 Jun 2007 15:09:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jun 2007 15:09:24 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.225 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: 64.233.162.225 nz-out-0506.google.com Linux 2.4/2.6 Received: from [64.233.162.225] ([64.233.162.225:32827] helo=nz-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 75/6A-47650-A81F7764 for ; Tue, 19 Jun 2007 11:09:20 -0400 Received: by nz-out-0506.google.com with SMTP id i11so1566790nzi for ; Tue, 19 Jun 2007 08:08:43 -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=mwHZGZw2bsmNC69NZgVuZcBrT/0K0MfqLoxTMPjnJNSnFxpdcj70CgAXgsWb+/CAKgfNHnOsVJHC+/3RdM2VxVq8p/4Ort/f693R5C/q0sFHF/ILhMBm8W3rD/YiMwm7VIxTJsIsPz+WuZBYX+9sOQuDBw8GcaJfcj+1Dwg8oyQ= 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=kvJX784QEb9C11sg3Ee1JEQtl3+cqVtmZQBSoO7e/meAeOhdkqafAkAM/VtBNbvmGP9ztB5ncwzW4asdgtx84Cub5tca6StofYhlrz6NzeSg0DPM5LFDoghNjHgyeKqqOELEQXqvTz8em6r++MlQ7a5ktprqihKUkVck7RDiOUU= Received: by 10.143.18.6 with SMTP id v6mr374223wfi.1182265723295; Tue, 19 Jun 2007 08:08:43 -0700 (PDT) Received: by 10.114.47.2 with HTTP; Tue, 19 Jun 2007 08:08:43 -0700 (PDT) Message-ID: Date: Tue, 19 Jun 2007 17:08:43 +0200 To: "Rasmus Lerdorf" Cc: "Peter Brodersen" , internals@lists.php.net In-Reply-To: <4677E7B1.2080305@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> <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com> <4671F184.2020401@lerdorf.com> <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com> <4677E7B1.2080305@lerdorf.com> Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6? From: pierre.php@gmail.com (Pierre) On 6/19/07, Rasmus Lerdorf wrote: > But this is no different from writing code that will work on both PHP 5 > and PHP 6. The only difference is that instead of checking for PHP 5 > you will be checking for Unicode. Like I said, we don't want the > Unicode decision to be synonymous with PHP 5 vs. PHP 6 because then the > non-Unicode folks will never get the benefits of the non-Unicode > improvements in PHP 6 and we would be forced to support PHP 5 for a lot > longer. We really stretch our already thing resources in order to > support multiple branches, so anything we can do to get as many people > as possible onto the same codebase helps us a lot. Just as a last (hopefully) comment, even if nothing seemed to have an influence, no matter how many we are to prefer a unicode only mode (so far only you are in favour of it, maybe Andree too but I don't remember his opinion on this topic :). The gain we hope to have by keeping a non unicode mode is about having more users moving to PHP6. I would like to know why it will work better than with php5, any thoughts? And let forget that maintaining (and develop/implement) these two modes will obviously take more time. Cheers, --Pierre