Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23359 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73692 invoked by uid 1010); 15 May 2006 09:31:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 73676 invoked from network); 15 May 2006 09:31:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2006 09:31:28 -0000 X-Host-Fingerprint: 195.225.34.5 fw01.axit.nl Received: from ([195.225.34.5:6866] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 8D/1F-19568-F6A48644 for ; Mon, 15 May 2006 05:31:27 -0400 Message-ID: <8D.1F.19568.F6A48644@pb1.pair.com> To: internals@lists.php.net References: <138663365.20060514205903@marcus-boerger.de> <4468231D.6000604@php.net> <207855155.20060515090128@marcus-boerger.de> <44682CC8.6010200@php.net> Date: Mon, 15 May 2006 11:31:06 +0200 Lines: 33 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Posted-By: 195.225.34.5 Subject: Re: [PHP-DEV] E_ALL changes in 5.2/6.0 From: r.korving@xit.nl ("Ron Korving") Wouldn't it be nice to start a PEAR2 (or 5) then, with PHP5-ready code, where PHP5 features will actually be used and backwards compatibility for PHP4 is lacking. The current PEAR could gradually be ported into this, and PHP4-users can continue to use PEAR (version 1, if you will). Ron "Lukas Smith" schreef in bericht news:44682CC8.6010200@php.net... > Marcus Boerger wrote: > > >> Sorry i have to say that but PEAR is no argument here as still after >> years of PHP 5 there is no PHP 5 compatible PEAR. Yet we are discussing >> a PHP 5 version here. > > PEAR is PHP5 compatible. But you probably meant E_STRICT compatible. Yes, > I agree that PEAR needs to become once again a place for features missing > in PHP and not a place for legacy code. > > > Anyways I brought up PEAR more as an example of what our current userbase > looks like. Mostly doing PHP4 and where its PHP5 its often written to also > be compatible with PHP4. By increasing the burden on keeping this > "duality" we might get more people to make the jump which might put enough > pressure on hosters to finally break the chicken and egg situation with > PHP5. > > regards, > Lukas