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

PHP 6 will come with some big changes. We could have a compat flag that supports old-style classes PhpDate if needed. In any case, it's premature as we don't have this yet and it's not relevant to PHP 5. I just wanted to Fyi that it's something to consider. Andi > -----Original Message----- > From: Steph Fox [mailto:steph@zend.com] > Sent: Tuesday, July 18, 2006 1:00 PM > To: Andi Gutmans; 'Derick Rethans' > Cc: 'Edin Kadribasic'; 'Dmitry Stogov'; > internals@lists.php.net; 'Ilia Alshanetsky' > 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) > > > Although we already have quite a few classes in PHP I think we are > > still at an early point and we should make the right > decision now. I'd > > prefer that from now on going forward we prefix all new > classes with > > Php. In PHP 6, once we implement namespaces for classes (yep, on my > > todo) then we can put those classes in a Php namespace. > > I'm probably being dim here, but how is this going to pan out > for BC? Either now, or when PHP 6 comes along and we > (presumably) go from PhpDate to Php::Date? (What am I missing?) > > This does leave some existing inconsistencies > > with SOAP/XML but honestly, we're catching it MUCH earlier > than we did > > with functions, so we'd be in pretty good shape. > > A few more than that... > > > My $.02 and hopefully we can have a more focused discusion > now, which > > isn't geared against Derick, but forward looking and > considering all > > the other classes that will be coming down the pipeline and > doing the > > right thing. > > Andi >