Hello Greg, Monday, May 15, 2006, 12:51:16 PM, you wrote:
> Steph Fox wrote: >> Marcus, >> >> FWIW I'm with you (unusually) over E_STRICT. Why would anyone have E_ALL >> switched on anywhere but a dev box? - and when there is the option to >> switch on E_ALL without E_STRICT, it makes it much easier to miss >> useful information about the direction PHP is going in. >> >> Pierre: the biggest E_STRICT issues I'm aware of are the 'vars don't >> live here any more' one (which was removed two months ago in PHP_5_1 >> branch) and the 'only variables can be passed by reference' one (which >> is in PHP 4.4.* anyway). Beyond those two, it ought to be pretty rare > Side note: calling functions statically that do not have a static > modifier causes E_STRICT. Hello PEAR::isError() > This is of course going to be a fatal in PHP 6, but it is now the most > common E_STRICT I see in PHP4-based code. > I agree that it is appropriate to change something like this in a 5.X.0, > but it will be a headache for anyone running legacy apps (not just > PEAR). Until someone writes some killer apps in PHP5 to replace phpBB > and company, changes of this nature will simply prevent moving to PHP5 > but that's another story and not the concern of internals (I agree with > this strongly). If you all are willing to deal with the fallout (think > PHP 4.4) then that's that. Ones again E_ALL is for development. For example to move PEAR code to PHP 5. It is not for running legacy apps. IF you guys want i'd be ok with adding a new mode say "E_RUN"... Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
