Derick Rethans wrote:
I didn't say that my code is more important, but if we don't get the
date class now, we will get it in 5.1.1 and then break your code - so
You're stating this like a fact. Date _can_ be renamed, there's nothing
sacro-sanct about this class.
Just to illustrate some question which could be raised to weaken your
point that Date is the one and only name for that class:
Why does it include time as well, shouldn't it be Datetime (a la SQL)?
Is it going to be the only class in ext/date (no, there is already
timezone)? => Shouldn't it be Date_Timezone and Date_Date/Date_Datetime
then?
By the same logic the function file_get_contents() could be called get().
?
Because I personally feel that get() would be the right name for it the
same way you feel Date is the right name for your class.
No no, the core reserves the right to name whatever they want, it's the
userland code that is responsible for prefixing their classes.
Is that why function names were prefixed? Or __get?
You sure have the right to introduce whatever you want but is it also
*smart* to insist on a specific name if you could easily avoid conflicts?
PHP moved on from "what is legal" to "what is right" a long time ago IMHO.
As soon as we have separate namespaces for core/application classes we
can talk how to resolve issues like that again but for now I'd highly
appreciate if you'd take a more conservative approach.
Cheers,
- Chris
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
