Can we start concentrating on finding a real solution to BC breaks
rather than throwing them out there and everyone complaining?
define(php5) {
stuff that breaks in php6
}
define(php6) {
stuff that doesnt work in PHP5
}
It would be nice to back port this to PHP4, but at least make the future
BC Breaks more bareable...
Regards
Alan
Christian Schneider wrote:
One caveat with making a static call to a non-static function a fatal
error is that it will make use of static calls impossible for code
which wants to be PHP4 and PHP6 compatible, no? You probably don't
care but I still wanted to mention it.
E_STRICT is nice for people who are able to move their code base to
pure PHP5 but not everybody can do that. Which means that converting
E_STRICT to E_FATAL should be done with care. But it's obviously up to
you guys to decide when the grace period is over...
Oh, one thing which would help would be if certain E_STRICT errors
could be (optionally) reported at compile time to not have to depend
on code coverage tests. E.g. A::foo() could (optionally) report an
E_STRICT if class A with a non-static method foo is already defined
when encountering the call. Maybe the lint-mode could be used for that.
PS: There are no plans to make non-static calls to static methods
illegal, right?
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
