Stanislav Malyshev wrote:
I would consider making internal class names illegal
in namespaces. this would be consistent simple and clear.
It's one of the options, but I'm not sure it's the best one. Opinions
welcome.
I don't think that's a good solution because that kind of defeats the
reason we want to introduce namespaces in the first place: I can name my
classes without having to be afraid of a name clash later on when PHP
adds new classes.
Unless the restriction only applies to the current (global) internal
classes and all new classes are going to be introduced within a PHP
reserved namespace (e.g. PHP::Date instead of Date or the like) while
not adding more names to the list of illegal names. And even then I
would prefer no restriction and give the programmers full freedom of
naming within their namespace.
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
