Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:31002 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75700 invoked by uid 1010); 17 Jul 2007 15:28:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 75652 invoked from network); 17 Jul 2007 15:28:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jul 2007 15:28:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 212.112.227.169 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.5 (sometimes 2.4) (4) Received: from [212.112.227.169] ([212.112.227.169:46694] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 59/A3-46997-620EC964 for ; Tue, 17 Jul 2007 11:28:39 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id D8E24A58024; Tue, 17 Jul 2007 17:28:34 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (flottensignalgeber [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01715-09; Tue, 17 Jul 2007 17:28:32 +0200 (CEST) Received: from [192.168.1.46] (49-120.5-85.cust.bluewin.ch [85.5.120.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ipx11223.ipxserver.de (Postfix) with ESMTP id 1AD8BDF0094; Tue, 17 Jul 2007 17:28:32 +0200 (CEST) Message-ID: <469CE00D.5030307@pooteeweet.org> Date: Tue, 17 Jul 2007 17:28:13 +0200 User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Andi Gutmans Cc: Ilia Alshanetsky , jani.taskinen@iki.fi, internals@lists.php.net References: <698DE66518E7CA45812BD18E807866CE648191@us-ex1.zend.net> <54C4340A-D9EA-4B5A-B39C-B55B29B1B3BC@prohost.org> <698DE66518E7CA45812BD18E807866CE648193@us-ex1.zend.net> <469B7FB1.1070507@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE648290@us-ex1.zend.net> <469C6436.2060009@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE6483DF@us-ex1.zend.net> <469CD717.2070607@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE6483EC@us-ex1.zend.net> In-Reply-To: <698DE66518E7CA45812BD18E807866CE6483EC@us-ex1.zend.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] POSIX regex From: mls@pooteeweet.org (Lukas Kahwe Smith) Andi Gutmans wrote: > Hmm I don't quite understand what bad code vs. good code plays here. > Wordpress is one of the most popular applications out there so it's got > huge value to our community. I bet there's a huge amount of PHP > applications who's source code is of the same quality or worse. Anyway, > the issues I have seen would also be relevant to what you call "good" > code but again, when it comes to compatibility, I don't quite know why > that will play a big role. Bad good in the sense its messy. But what I was going at is that I find your proposed list good with the exception of SugarCRM. It might be good to also include a php5 only app, so that we have a good idea of how messy code, fairly procedural, E_STRICT complaint etc code ports to PHP6 unicode==off. > I am talking about porting to both unicode_semantics=off and on. This > will give us a good understanding of the difference of the modes and > where we're at. I bet most people who are voicing their opinions have > actually not tried to write a sizeable application with PHP 6 and also > tried to run an existing one on PHP 6 > (unciode_semantics=on). I can also do some performance testing in our ok .. this makes this quite a large undertaking indeed. regards, Lukas