On Wed, Dec 31, 2008 at 20:12, Marcus Boerger <he...@php.net> wrote: > Hello Lars, > > Wednesday, December 31, 2008, 6:59:08 PM, you wrote: > >> Hi Markus, > >> have you measured the performance impact in a class with - say - ten >> methods? And what to do with __get() and __call()? How are the >> prioritized in the method resolve order? > > Translated into user code we now have: > > public function __zend_call($name, $args) { > // Added property lookup > if (isset($this->$name)) { // may call __isset > $callable = $this->$name; // may call __get
Uhmm. I hope I got this wrong as: class foo { function __isset() { return true; } function __get() { return "hello world"; } function __call() { } } $foo = new foo; $foo->foobar(); will first execute __isset(), then __get() and then __call()? That is a major backwards compatibility break, and increases the inconsistency and decreases readability 10times -Hannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php