rfc:namespaceresolution
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
rfc:namespaceresolution [2008/11/04 19:18] – lsmith | rfc:namespaceresolution [2013/10/29 17:40] – -> Implemented nikic | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2008-10-30 | * Date: 2008-10-30 | ||
* Author: Lukas Smith < | * Author: Lukas Smith < | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
This RFC discusses the way identifiers inside a namespace are to be resolved that are not fully qualified. | This RFC discusses the way identifiers inside a namespace are to be resolved that are not fully qualified. | ||
+ | |||
===== Introduction ===== | ===== Introduction ===== | ||
Line 37: | Line 38: | ||
===== Possible approaches ===== | ===== Possible approaches ===== | ||
- | |||
==== Fallback to the global namespace ==== | ==== Fallback to the global namespace ==== | ||
In this scenario when an identifier does not resolve inside the current namespace and attempt would be made to find the identifier in the global namespace. | In this scenario when an identifier does not resolve inside the current namespace and attempt would be made to find the identifier in the global namespace. | ||
- | When referencing global identifiers in namespaces, it is probably a reasonable assumption that the bulk of that will be function calls. This is because currently most functionality in PHP is provided via functions. Also once an instance of a class has been made, one does not have to reference the identifier again in common usage (obviously | + | When referencing global identifiers in namespaces, it is probably a reasonable assumption that the bulk of that will be function calls. This is because currently most functionality in PHP is provided via functions. Also once an instance of a class has been made, one does not have to reference the identifier again in common usage (there will still be cases, like with instanceof/ |
In the past people often created classes for the sole reason of being able to sort of " | In the past people often created classes for the sole reason of being able to sort of " | ||
Line 48: | Line 48: | ||
One noteworthy aspect here is that for classes we have autoload. If non fully qualified identifiers can be used to reference global identifiers, | One noteworthy aspect here is that for classes we have autoload. If non fully qualified identifiers can be used to reference global identifiers, | ||
- | For functions however we do not have autoload capabilities. This brings the advantage that falling back to the global namespace does not run the performance risk of autoload. So a fallback would be much less expensive, but obviously | + | For functions however we do not have autoload capabilities. This brings the advantage that falling back to the global namespace does not run the performance risk of autoload. So a fallback would be much less expensive, but there would still be overhead for not making intentional references to the global namespace fully qualified. |
At the same time the ability to automatically fallback into the global namespace gives the ability to overload global identifiers inside a namespace without having to modify existing code inside that namespace. This however can also be considered dangerously similar to the ambiguity issues we solved by changing the namespace separator (for example static code analysis becomes more difficult). | At the same time the ability to automatically fallback into the global namespace gives the ability to overload global identifiers inside a namespace without having to modify existing code inside that namespace. This however can also be considered dangerously similar to the ambiguity issues we solved by changing the namespace separator (for example static code analysis becomes more difficult). | ||
Line 72: | Line 72: | ||
</ | </ | ||
- | One approach to make it at least noticeable when a fallback into the global namespace occurs would be to throw an E_NOTICE in this case. This would obviously | + | One approach to make it at least noticeable when a fallback into the global namespace occurs would be to throw an E_NOTICE in this case. This would discourage users from using the fallback for overloading, |
Another approach to reduce (though it does not remove the issues entirely) some of the issues is by simply removing functions (and constants) from namespaces. | Another approach to reduce (though it does not remove the issues entirely) some of the issues is by simply removing functions (and constants) from namespaces. |
rfc/namespaceresolution.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1