Re: fatal static call in php 6.0?

From: Date: Thu, 25 May 2006 11:47:24 +0000
Subject: Re: fatal static call in php 6.0?
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.internals 
Request: Send a blank email to internals+get-23646@lists.php.net to get a copy of this message
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

« previous php.internals (#23646) next »