Marcus Boerger wrote:
whatever the patch looks like, it is a change from 5.0.0's E_STRICT
I was just noticing a probable bug in the patch and felt like reporting it, that's all. I didn't want to start a discussion about migration paths but since you asked for my opinion, here it is...
to a E_COMPILE_ERROR and actually fixes another problem. This raises an interesting question. How long must we wait until we can follow the E_STRICT idea and change a specific E_STRICT into a fatal error. Must it be until eternity?
Programming is like sex: One mistake and you have to support it for the rest of your life ;-)
But more seriously: You have to realize that in the real world things move much, much slower than at internals here. We just tried PHP 5 for our site here and realized that we don't have the resources to make the necessary changes to get things running right now. This, combined with the fact that PHP 4 works fine for us made us decide to delay an upgrade once again. And while you're moving on to add more incompatibilities we don't even have the resources to do the 4->5.1 transition yet. And I bet we're not the only ones.
Maybe it would help if people at leat from time to time use PHP 5 and especially with E_STRICT on for development. For example Zend Framework has it even as a requirement.
I tried that here and it didn't really help me: E.g. it reported that is_a() should be replaced by instanceof but as we have to keep the code PHP 4 compatible (and it is only run on PHP 4 on production machines anyway) it just doesn't make sense to change anything there at this time.
- Chris -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
