Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20788
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 28 Nov 2005 23:38:21 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <911930939.20051128233821@marcus-boerger.de>
To: Jessie Hernandez <jrhernandez05@gmail.com>
Cc: internals@lists.php.net
In-Reply-To: <0D.A2.21657.EFE7B834@pb1.pair.com>
References: <0D.A2.21657.EFE7B834@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Basic Namespace Requirements
From: helly@php.net (Marcus Boerger)

Hello Jessie,

  i already showed that dropping constants in namespaces leeds to static
classes or private classes. So we are just shifting here. Instead of doing
work that is worth nothing you should simply try to come up with a working
patch using a working separator which can clearly only be "\".

best regards
marcus

Monday, November 28, 2005, 11:04:43 PM, you wrote:

> All,

> After seeing Dmitry's patch, all he is allowing inside a module are import
> statements and classes.

> So, the question is, can we scrap both namespace constants and namespace
> functions and just stay with classes (as was agreed on several months ago,
> Andi himself agreeing to it)? This would make the patch smaller, simpler,
> AND would allow me to reuse the "::" operator (and there would be no
> conflicts with ternary operations).

> I think this is the best solution thus far. If any one of you still feels a
> need for constants/functions, PLEASE show me a _valid_ example that cannot
> be accomplished by just simply putting the constant/function inside a class
> in the namespace.

> If I don't hear of any valid arguments, then I'm going to go ahead and scrap
> constants and functions and then concentrate on the final details of the
> patch.


> Regards,

> Jessie Hernandez




Best regards,
 Marcus