Hello John, where is the problem in having it as 'DateTime' or 'Date' in namespace 'PHP' and as 'PHPDateTime' or 'PHPDate' in the global namespace? We do not have namespaces now but there is no technical reason to prevent that from the beginning. So there is no preoblem here move a long forget about namespaces and solve the problem at hand. The class needs to go in with a that is accetpable now. And not once namespaces are at hand.
best regards marcus Wednesday, July 19, 2006, 4:14:59 AM, you wrote: > On Wed, 2006-07-19 at 03:58 +0200, Steph Fox wrote: >> John's right, because PHP::PHPDateTime would have to become acceptable >> syntax. Not the _only available_ syntax, but an acceptable one. > Unless you're proposing that we automagically parse class names so that > $a = new PHP::DateTime(); > $b = new PHP::PHPDateTime(); > are really references to the same class (which I think is a horrible > idea) you'll either need: > <?php > import PHP; > $a = new PHPDateTime(); ?>> > which seems redundant or... > <?php > $a = new PHP::PHPDateTime(); ?>> > which is just wonky.. Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
