Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37758 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22142 invoked from network); 20 May 2008 20:20:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 May 2008 20:20:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=steph@zend.com; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=steph@zend.com; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain zend.com does not designate 64.97.136.166 as permitted sender) X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 64.97.136.166 smtpout0166.sc1.he.tucows.com Solaris 8 (1) Received: from [64.97.136.166] ([64.97.136.166:2966] helo=n066.sc1.he.tucows.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/15-28995-A8233384 for ; Tue, 20 May 2008 16:20:27 -0400 Received: from sc1-out02.emaildefenseservice.com (64.97.139.2) by n066.sc1.he.tucows.com (7.2.069.1) id 4769F91801152B37; Tue, 20 May 2008 20:20:24 +0000 X-SpamScore: 2 X-Spamcatcher-Summary: 2,0,0,386c5b4221041e55,cfc06c81b00088e0,steph@zend.com,-,RULES_HIT:152:355:379:539:540:541:542:543:567:599:601:947:967:973:982:988:989:1155:1156:1260:1277:1311:1313:1314:1345:1437:1515:1516:1518:1534:1541:1587:1593:1594:1676:1711:1730:1747:1766:1792:2073:2075:2078:2393:2559:2562:2893:3027:3353:3622:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:4250:5007:6117:6119:6261:7875:7903,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0, MSF:not bulk,SPF:,MSBL:none,DNSBL:none,TSO:0 X-Spamcatcher-Explanation: Received: from foxbox (host86-137-246-48.range86-137.btcentralplus.com [86.137.246.48]) (Authenticated sender: steph.fox) by sc1-out02.emaildefenseservice.com (Postfix) with ESMTP; Tue, 20 May 2008 20:20:23 +0000 (UTC) Message-ID: <02e701c8bab7$19a3dd10$4401a8c0@foxbox> Reply-To: "Steph Fox" To: , "Edward Z. Yang" References: <7d6e34d80805191240k64cb1ba6k3e8f7a50ddf068c@mail.gmail.com> <4831F27B.7030001@suse.de> <296949B4-D328-49FE-968B-4942B28FE869@pooteeweet.org> <7d6e34d80805191454m69614624v7a05037fa947328e@mail.gmail.com> <698DE66518E7CA45812BD18E807866CE019F60DE@us-ex1.zend.net> <34.64.28995.1BE23384@pb1.pair.com> Date: Tue, 20 May 2008 21:21:32 +0100 Organization: Zend Technologies MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PHP-DEV] Unicode progress [Was: unicode.semantics ad infinitum] From: steph@zend.com ("Steph Fox") Hi Edward, > As I a PHP developer on Windows, I pay very close attention to > development work on PHP and regularly test my code against PHP 5.3, > hand-built from the CVS. Nearly all of the PECL extensions are broken on > Windows for PHP 6. The http extension has a very nasty problem: its > fatal error appears to loop nearly ad infinitum. This makes compiling > snaps locally very difficult--I've given up. Why is the log file 4.4 MB > long? Because nobody's been trying to compile snaps against PHP 6? Basically most extension developers decided to stay with 5_3 for now and haven't migrated their code to work with Unicode on. I would hope, though, that if PHP 6 is Unicode-only there might be more enthusiasm for adapting code to work with it. > Also, as stands it appears most non-trivial applications are fairly > broken. Those issues need to be resolved first, before we toss Unicode > onto the pile. I think the test script and ZE problems should be resolved first... plus I just discovered that my php.ini isn't being found when I run commandline tests (e.g. php -r "var_dump(strcasecmp());" doesn't throw an error unless I explicitly set error_reporting from the commandline, despite having E_ALL|E_STRICT in the INI). These are basic things, nobody can really go much further until they're fixed. So I agree with you - it's far too soon for apps testing at this stage. - Steph