Re: E_ALL changes in 5.2/6.0

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" <lsmith@php.net> schreef in bericht news:44682CC8.6010200@php.net... > Marcus Boerger wrote: > > <offtopic> >> 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. > </offtopic> > > 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