Tony Bibbs wrote:
While I could munge the class names in one or more packages as you
suggest then I'm in maintainability hell because when I need to update
one of the other packages (for security, features or bugfixes) you have
to do the name munging again.
C'mon, that ain't right. Next excuse?
Sorry. I'm assuming here that you are giving your class names
'prefixed' names. Like Zend Framework is doing.
For what it's worth, >10 years ago we were in this same position with
Smalltalk; and specifically, IBM Smalltalk. Tradtional Smalltalk does
not have namespaces. And neither did ours - we were traditional :-)
So, we used product prefixes. We had a relatively hugemongous class
library, a fairly large, distributed team, and just a handful of
prefixes. It was 'ugly', to some extent, but it did work.
Later, we added namespaces. I never used 'em. Not sure if anyone did.
We added them because the masses roared for them. I don't think they
used 'em either. Because they were kinda horky. (Be careful what you
ask for, because you might just get it)
Point is, if you're doing OO in the usual fashion, the only time you
need to reference globally scoped names is when you reference the class
itself, which is when you invoke constructors, or call static methods.
Instance method invocation was used waaaaaay more often than those two.
--
[EMAIL PROTECTED]
IBM PHP Community Architect, IBM Research Triangle Park
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
