Larry Garfield wrote:
One catch here is that E_STRICT implies no PHP 4 compatibility, as E_STRICT chokes on PHP 4-style class usage, etc. Drupal 6 had PHP 4 compatibility so E_STRICT was not an option. The core system was developed to E_ALL standards, but not all add-on modules (which are the lifeblood of any modular framework) are. I cannot speak for other projects but since Joomla, Wordpress, and CakePHP all were PHP 4-friendly until their most recent versions at least I suspect the story is much the same.
I came to the game JUST as PHP5 was creeping out into production, and so never ran PHP4 locally, however all of the projects I've been involved with have run happily on PHP4 and any code I've added has had to be compatible. It has taken several months to 'accommodate' PHP5.3, and some projects STILL will not run cleanly with it, so while people are pushing changes that THEY think are good ideas, please also bear in mind that PHP4 IS only just starting to be replaced, and PHP5. provides a cleaner base to move that code forward to!
Now that we have 'lost' the target of PHP6, maintaining a stable platform for the time being is VERY important! Currently PHP5.2 is that stable platform.
-- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
