Re: Re: PEAR::Date broken (Was: [PHP-CVS] cvs: php-src(PHP_5_2)/ext/date php_date.c php_date.h)

From: Date: Wed, 19 Jul 2006 19:41:07 +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  Groups: php.internals 
Request: Send a blank email to internals+get-24721@lists.php.net to get a copy of this message
On Wed, 19 Jul 2006 14:02:56 -0400 john@coggeshall.org (John Coggeshall) wrote:
On Wed, 2006-07-19 at 09:40 +0200, Marcus Boerger wrote:
A single alpha released pecl extension has a problem, well that imo is not that bad conflict and can be solved before it is being released.
I wonder if The Perl guys check every single CPAN extension before introducing a new keyword or identifier... you know, just in case...
It is not about checking every project out there but how to deal with the new classes, planed or not. There was not clear policy about that and we still don't have one. "They" are choosing to rename it, fine. But we still have to discuss once and for all what to do with all new classes and how to inform our users.
Agreed, there isn't clear policy. But I think if it's generally been agreed that 'DateTime' is acceptable for the main class in PHP's date extension, a precedent was just created that says the names of classes should be _prefixed_ with the extension name. (I'd hoped the name of an extension's root class would be _equal_ to the PHP extension name, purely because that's more intuitive for users, but not so). Also invoking precedence, there are no underscores in PHP's internal classnames.
We also have to discuss how to avoid such events to happen again.
With SPL and now Date having those prefixes for their internal classes, I doubt the need for further discussion. It just needs setting in stone somewhere, no? - Steph
Cheers, -- Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php __________ NOD32 1.1380 (20060125) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com __________ NOD32 1.1380 (20060125) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com


« previous php.internals (#24721) next »