Re: Re: PEAR::Date broken (Was: [PHP-CVS] cvs: php-src(PHP_5_2) /ext/date php_date.c php_date.h)
| From: | John Coggeshall | Date: | Tue, 18 Jul 2006 19:43:17 +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 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-24512@lists.php.net to get a copy of this message | ||
On Tue, 2006-07-18 at 20:25 +0200, Edin Kadribasic wrote:
> But breaking even a few or "both" is still reckless, irresposible
> behaviour when all that is needed to fix the breakage is rename the
> class. Espacially because of all the bad publicity we get for breaking
> backwards compatibility for no good reason.
In my experience, we've received an equal if not greater amount of
negative publicity from a lack of consistent naming conventions. PEAR is
a library of functionality developed on top of PHP, and therefore PHP
has the first say to what to name what and everyone else moves around
that. I also think that as PHP moves from a strictly procedural language
to an ever growing OO arm, IMHO it isn't unreasonable to lay claim to
certain core class names. Moreover, I think this whole flame war is
counterproductive for us all -- can we just do a +/- vote on this and
move on to more useful concerns?
+1 for Date as the name.
John