Derick Rethans wrote:
On Fri, 25 Nov 2005, Sascha Schumann wrote:
    I move that the class is renamed for the time being as to not
    conflict with existing codebases, and release 5.1.1
    expediently.

I second that. Otherwise 5.1 is a dead branch lots of people won't update to.

Yes, and that will break code again as I just explained to Sebastian Kettler. And it will break *my* code ;-)

Does that mean your code is more important than all the lines of code out there? You must be kidding.
And as you stated yourself your code hasn't  even been released yet.

Besides that, using "Date" and "Timezone" as classnames are the most sensible names for those classes and I do not think we should have change that.

By the same logic the function file_get_contents() could be called get(). Using generic names for core functionality in the global name space is a bad thing, no matter how convenient the name might be. That's a lesson PHP has learned for function names quite a while ago, let's not repeat the same mistake for class names.

And let's undo the slip before more harm is done.

- Chris

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

Reply via email to