-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to fully qualify class names #37
Comments
The patch still needs quite some work. All the array_search() / friebe, Fri, 02 Sep 2005 18:08:18 +0200 |
The patch does not work correctly for situations in which class A friebe, Mon, 12 Sep 2005 10:17:23 +0200 |
Fixed the patch - net.xp_framework.unittest.reflection.ReflectionTest friebe, Tue, 04 Oct 2005 23:48:42 +0200 |
Maybe implements() should not be backwards compatible? BC causes friebe, Tue, 04 Oct 2005 23:59:54 +0200 |
Revamped lang.base.php and lang/ClassLoader.class.php committed to friebe, Wed, 28 Dec 2005 16:10:19 +0100 |
New patch available at above location. Also passes all tests. friebe, Mon, 20 Feb 2006 13:05:21 +0100 |
Migrated to PHP5, rewrote parts of this RFC friebe, Fri, 16 Feb 2007 12:06:31 +0100 |
To be deprecated in XP 6 - see #172 |
Removed support for uses(), global and xp-framework/rfc#37 class names
Scope of Change
Classes can be optionally declared with their fully qualified name. Class
loading and reflection semantics will not change, though.
Rationale
Avoid name clashes. Especially useful for supporting classes that never
appear in a new statement or any other place their full name needs to be
typed, like remote interfaces.
Functionality
A class declares being within a package by setting the variable $package.
Example (Declaration)
Example (Usage)
Output of above example
Notes
Security considerations
n/a
Speed impact
Core will become a bit slower because it will need to distinguish between
the two cases:
Dependencies
Related documents
Experiment
The text was updated successfully, but these errors were encountered: