On 10/09/06, dAniel hAhler <[EMAIL PROTECTED]> wrote:
Marcus Boerger wrote:
> it hasbeendiscussed and the conclusion is that it isfar too much of a
> slowdown for every function call and thus we are not going to implement
> it.
Maybe a dump question, but wouldn't it get considered only, AFTER PHP has
found that the function does not exist?
So, it shouldn't be a slowdown at all.
On the other hand I don't know the internals of PHP very much.
> The speed reasoning put aside we also found that procedural techniques
> should not mix too much with the object oriented features.
This may be a reason, but I for one would not think that this is "dirty".
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
One way in useerland to solve this is to use an error handler to
identify non existant function calls and then use an appropriate
mechanism to find them.
The only slowdown would be when an error occurred (but acceptable).
If the functions where kept in files of their own name, then this
would be the end of function libraries and a LOT of additional files.
This could promote refactoring to take groups of related functions and
convert them to a class to allow for autoloading to work.
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
