On 5-Nov-06, at 6:30 PM, Lester Caine wrote:

Ilia Alshanetsky wrote:

The language always has the best pick of namespaces, this is not just PHP, but ANY language. The fact we've made a compromise and allows PEAR to retain the date class IMO has been a horrible mistake, one hopefully not to be repeated in the future.

I never used the PEAR Date - it was crap - but all my applications failed with your new one BECAUSE Date was the obvious name for that package. I STILL can not see why we can't just select these things as I do in C++ and include your new function if I want or keep with my own established version - what ever the name. This new stuff does not HAVE to be hard coded into the core - simply loadable like any other good extensible language? If we don't want it we don't load it! I don't need any database stuff other than Firebird - therefore I want a DATE and TIME package that follows Firebird rules end of story.

You seem to be under the assumption that people care about what it is that you want, reality is that most people could care less. That said this is an open source project, so rather then pointless whining on the list you can always tweak the source code to your needs, such is the beauty of the open source software.

Ilia Alshanetsky

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

Reply via email to