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 01:34:12 +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  Groups: php.internals 
Request: Send a blank email to internals+get-24613@lists.php.net to get a copy of this message
We could put namespace support into 5.3. -Andrei On Jul 18, 2006, at 6:24 PM, Steph Fox wrote:
Andi Gutmans wrote: [snip]
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
This is a good solution. 3 extra characters for each class have not hurt spl users (no reports of SPL-related carpal tunnel syndrome yet, right? :). It will make it simple to figure out whether a class is internal (does it start with "Php?") and will eliminate all future debate. I have no qualms renaming the PEAR packages that I maintain that start with PHP_ if this decision is made.
I am not sure I like this idea of prefixing all the classes with PHP_. Having PHP_TextIterator seems kind of wonky to me. Besides, I don't really see any SPL_ prefixed classes, they are all either *Iterator or *Object. I could argue that Perl or Python don't do this prefixing, but I guess they do have namespace support.
Exactly, and that's the problem. We aren't dealing with 'no namespace support', we're dealing with 'no namespace support just yet but we'll have it in the foreseeable future'. We have to deal with both situations right now. - Steph
-Andrei


« previous php.internals (#24613) next »