Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41121
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.133 as permitted sender)
Message-ID: <003f01c92f8f$bcb706b0$3ffc1f3e@foxbox>
To: "Hannes Magnusson" <hannes.magnusson@gmail.com>,
	"Lester Caine" <lester@lsces.co.uk>
Cc: "PHP internals" <internals@lists.php.net>
References: <48F6B3C5.9030102@chiaraquartet.net> <7f3ed2c30810152312h5391b25dke2695362c8d28d3b@mail.gmail.com> <48F6E50E.4010107@lsces.co.uk> <7f3ed2c30810160009i70392f39wabd879295dad842b@mail.gmail.com>
Date: Thu, 16 Oct 2008 14:04:32 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] namespaces sanity: addition to RFC explaining why Stas's proposal doesn't work
From: steph@php.net ("Steph Fox")

Hannes, Lester...

>>> Can we please start small and then incrementally add more features?
>>> Lets start with classes only in namespaces in 5.3.
>>
>> The problem with that statement is that if it is used to ignore the other
>> problems, then at some point it may be necessary to re-write all the new
>> namespace code simply to allow additional features to be added!
>
> tough luck. If it needs total rewrite in the future then it needs
> total rewrite now to support the additional features anyway.

That was my argument for the entire first half of this week. If either of 
you had looked at Greg's latest idea, you'd know that it removes that 
problem entirely.

Please go and look at his proposals at 
http://wiki.php.net/rfc/namespaceissues, and then vote?

Thanks,

- Steph