On Tue, 2006-07-18 at 18:58 -0700, Rasmus Lerdorf wrote:
> > Regardless, we know it's coming and we know it'll have namespacing
> > support. If we do PHPDateTime right now we'll have PHP::PHPDateTime
> > later, and that's just wonky.
>
> Why would it be PHP::PHPDateTime ? An extra alias here isn't going to
> hurt very much. We are not talking about hundreds of classes. At this
> point we are talking about one with a very common short name.
Perhaps it's only an assumption, but I would think that "core" PHP
classes would fall into some sort of standardized namespace ala
ext/standard.. be it PHP:: or STD:: or whatever...
PHP::Date
PHP::Dir
PHP::Zip
PHP::Whatever
So, unless you are proposing that we call it PHPDateTime now and rename
it to PHP::DateTime later you'll end up with PHP::PHPDateTime if we
start prefixing things with PHP* now. If the argument is that it "makes
sense" that what used to be PHPDateTime is now PHP::DateTime I'll agree,
but what could have been
<?php
// My old PHP 5.2 script using DateTime
// Make it PHP 6 compatible
import PHP;
class foo extends DateTime {
}
?>
will now be a much more painful search/replace annoyance. To me that's a
huge win longterm.
John
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
