Hello Andi, passing $this to a static function is a different set of problems calling trouble on another front. If you pass $this to a static function you sooner or later pass it as $this and sooner or later you call back into the object scope from that $this. Now the trouble is that suddenly we have two $this. The obejct $this which is a pseudo variable controlled by the engine and which cannot be overwritten and $this in the local symbol table. The one that can be changed and even unset. I am quite sure the engine is not designed to take care for this situations in all places. That said sooner or later the same people complaining now will shout at us: hey you stuff sucks - fix it.
marcus Tuesday, May 16, 2006, 4:41:33 AM, you wrote: > I don't see why it has to be a fatal error. If there's an instanceof > relationship we can keep $this. If not, we should not pass $this > (which I believe we already do in PHP 5), in which case the author > would have to pass $this if he wants to change public properties. > Andi > At 12:49 PM 5/15/2006, Edin Kadribasic wrote: >>Todd Ruth wrote: >>>I don't see benefits of making semi-static fatal that make it >>>worth keeping those of us with large apps that depend on semi- >>>static from upgrading to php6. >> >>My sentiments exactly. OO purity/strictness do now work well with >>PHP's main strength -- its dynamicity. >> >>Edin >> >>-- >>PHP Internals - PHP Runtime Development Mailing List >>To unsubscribe, visit: http://www.php.net/unsub.php Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
