On 7/18/06, Steph Fox <[EMAIL PROTECTED]> wrote:

Thanks for the clarification. Sounds like a mess :)

Yes indeed. And yet, I don't think a non-messy way exists. This is a
particular case, since we do not have namespaces and have to find a
trick to:

1) Not clash with easily written class names (like DB, Query, String, ...)
2) Not cause a WTF reaction to cases like: "I can do a Time class, but
not a Date one?"
3) Find a way to reserve words with some kind of prefix.

And this before 6.0 as well as after 6.0 when we could have namespaces.

For object methods, PHP already reserved the prefix __, which was a
good decision at that time and allowed method to be added in other
releases.

The question now is to find a way for object names.

In the future, when everything will be prefixed with namespace, PHP
will have the opportunity to use any name inside PHP:: (or whatever
the name might be) without having to use PHP in the object name. At
that point in time, you won't have to come up with object aliases in
both global space and namespace.

By the way, I'm -1 for Date, even if I'd like to see it in core. The
problem isn't with the extension, it's with the name IMO.

Sincerely,
Olivier

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to