RE: [PHP-DEV] Re: PEAR::Date broken (Was: [PHP-CVS] cvs: php-src(PHP_5_2) /ext/date php_date.c php_date.h)
| From: | Andi Gutmans | Date: | Tue, 18 Jul 2006 21:00:12 +0000 |
| Subject: | RE: [PHP-DEV] 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-24538@lists.php.net to get a copy of this message | ||
Either of those are good options IMO, although we should make a high-level
decision if we want to do PHP prefix or we defer that to PHP 6.
Andi
_____
From: Ilia Alshanetsky [mailto:iliaal@gmail.com] On Behalf Of Ilia
Alshanetsky
Sent: Tuesday, July 18, 2006 1:49 PM
To: Andi Gutmans
Cc: 'Steph Fox'; 'Derick Rethans'; 'Edin Kadribasic'; 'Dmitry
Stogov';
internals@lists.php.net
Subject: Re: [PHP-DEV] Re: PEAR::Date broken (Was: [PHP-CVS] cvs:
php-src(PHP_5_2) /ext/date php_date.c php_date.h)
Given that PHP 6 far off target, I think we need to develop a solution that
works now. We've already waited too long given how many classes were added
in-core & extensions since 5.0 was released. Just like we have a naming
convention for functions we need to decide on one for classes as well. As
far as date class in particular, I think we just need to pick a
non-intrusive name for the 2 classes that extension offers and be done with
it.
And we need to get a bit on track as well. Let's outline possible options
for names, vote on them and move on to more important things.
The two naming options available so far are:
Option A: DateTime & DateTimeZone
Option B: PHPDate & PHPTimezone
More names are welcome.
Ilia Alshanetsky