On 7/19/06, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:


Because there is absolutely no reason to deliberately break our
installed base for a single version when it is quite arbitrary what we
call this class.  We know for a fact that calling it Date will be
problematic.  I also don't think a single alias is very hard to figure
out, but like I said, just choosing a slightly more descriptive name for
the class is probably a better solution all around.



Why not call it _DateTime or _Date?  maintaining it in the future for BC
will then be something like php::_Date, not too bad I don't think.

Reply via email to