Re: New Datetime class problem
| From: | Lester Caine | Date: | Sun, 05 Nov 2006 23:30:59 +0000 |
| Subject: | Re: New Datetime class problem | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26370@lists.php.net to get a copy of this message | ||
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. -- Lester Caine - G8HFL ----------------------------- L.S.Caine Electronic Services - http://home.lsces.co.uk Model Engineers Digital Workshop - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/ Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/index.php