Sorry to be a pain Andi, but...
I agree completely. Can't we just call the damn thing DateTime stick it
into
RC1 of PHP 5.2, and move on?
It doesn't entirely resolve the problem. There's another class in there too.
in ext/date:
typedef struct _php_date_obj php_date_obj;
typedef struct _php_timezone_obj php_timezone_obj;
<blah />
static zend_object_value date_object_new_date(zend_class_entry *class_type
TSRMLS_DC);
static zend_object_value date_object_new_timezone(zend_class_entry
*class_type TSRMLS_DC);
in PEAR::Date:
class Date
class Date_TimeZone
Do you really want DateTime_TimeZone in PHP for all time because otherwise
it'll clash with PEAR in PHP 5.2? How many machinations should we be
prepared to go through to avoid doing the obvious thing?
- Steph
Andi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
