On 04.11.2008, at 18:59, Gregory Beaver wrote:
#2 means we want to be able to access stuff like strlen() and
array_map() without any monkey business.
<snip>
functions/constants:
1) ns\func or ns\const
2) internal func\const
3) FAILBOAT
Right, for the most part people will want access to internal
functions, but what is the benefit of not including user space
functions/constants? I find this quite confusing. The resolution rules
should be easy to explain and it should be easy to understand what is
going to happen when reading code. Nobody knows all PHP internal
functions (especially as new internal functions can be defined by
enabling extensions), so expecting people to know what will or will
not fallback is kind funky.
So lets have a look about the disadvantages of including all functions/
constants:
1) you have to ensure the proper load order
2) .. ?
As you pointed out, there is no autoload for functions, so people are
accustomed to ensuring that all functions are loaded before usage. Am
I missing something?
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
