Ilia Alshanetsky wrote:
Avoid common namespaces and you'll make your application futureproof.
I'm still wary of this approach because it puts the burden on 99% of the code to be written (applications) instead of a small, controllable subset (core and libraries).
When developing a distributed application it is always a good idea to prefix functions/class names with app name or some acronym to avoid overly long names. The way things are going you are going to see more and more classes being introduced by "core" PHP as well as the growing
... which brings us back to the discussion of namespaces and which one core classes should use ;-)
number of PECL extensions out there and I am not even going to mention the thousands of libraries out there.
Those are less of a problem because you don't have to include them if you don't want to.
- Chris -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
