On Wed, 19 Jul 2006, Michael Gall wrote: > 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.
Except that it looks like a static private class property in the later following some published coding standards. And mangling the name with _ in front of it *is* quite a bit of a WTF factor. So no, this I hope nobody sees as a solution. Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
