Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33697
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 64.97.136.146 cause and error)
Message-ID: <048a01c836c6$da00d010$e6dfc350@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Derick Rethans" <derick@php.net>,
	"PHP Developers Mailing List" <internals@lists.php.net>
References: <alpine.DEB.0.98.0712042315260.20300@kossu.ez.no>
Date: Tue, 4 Dec 2007 22:41:44 -0000
Organization: Zend Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Dropping Namespace
From: steph@zend.com ("Steph Fox")

Hi D,

>   extension (DateTime, DateTimeZone). However introducing the new class
>   DateTimeSpan might break people's code that do things like:
>
> <?php
> use myNamespace::DateTimeZone as DateTimeZone;
> ?>

Typo? I guess you meant 'DateTimeSpan' to be in there somewhere...

This is I think the biggest problem with the implementation, that new 
internal classes can still break userland code. The problem of single-file 
namespacing is only a problem because of the performance implications for 
those who bundle their includes, and it _should_ be possible to find a good 
way to resolve that. I don't really see a problem with the 'use only at the 
head of the file' thing (although I know others do); in fact I prefer it, 
because it makes for an easier upgrade path.

Can I just ask one thing? If namespace support is once again pulled before 
it sees the light of a release, can we _please_ document exactly what the 
problems were, loud and clear, and put the document somewhere people are 
likely to see it?

Thanks,

- Steph