Re: Re: PEAR::Date broken (Was: [PHP-CVS] cvs: php-src(PHP_5_2) /ext/date php_date.c php_date.h)
| From: | Derick Rethans | Date: | Wed, 19 Jul 2006 07:20:12 +0000 |
| Subject: | Re: Re: PEAR::Date broken (Was: [PHP-CVS] cvs: php-src(PHP_5_2) /ext/date php_date.c php_date.h) | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-24647@lists.php.net to get a copy of this message | ||
On Wed, 19 Jul 2006, Michael Gall wrote:
> On 7/19/06, Rasmus Lerdorf <rasmus@lerdorf.com> 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