..snip > > Robert ... The main problem with the PHP5.3/4 changes are that the attitude > with PHP5.3 was 'you don't have to worry', but very quickly that became 'now > you do' simply by the switch of the default on e_strict. Perhaps when every > existing project is totally e_strict complaint things can be different, but > the amount of work needed to be carried out is simply not being achieved, so > we have to decide if we want to spend time fixing things like PEAR - my own > patches for which I've recently published - or simply switch off the problem > and disable e_strict? I know I've been banging on about this for a long time > - but I'm still trying to update my own and other peoples code to work > cleanly today :( It would be nice to see a few more people helping ... > rather than simply complaining at my moaning ... PHP created the problems > 'full stop' >
Ok, I believe your views have been expressed clearly and for the sanity of the mailing-list I'd consider stopping this thread. I would however suggest that you create an RFC which outlines exactly what you'd like to change and how you'd like to see it change and from there, a vote will ensue. -- David Coallier -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
