Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20791
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 28 Nov 2005 17:48:12 -0500
Reply-To: Jason Garber <jason@ionzoft.com>
Organization: IonZoft, Inc.
Message-ID: <675691196.20051128174812@ionzoft.com>
To: "Sara Golemon" <pollita@php.net>
CC: "\"Jessie Hernandez\"" <jrhernandez05@gmail.com>, internals@lists.php.net
In-Reply-To: <01d801c5f46a$ac03d450$5c8be5a9@ohr.berkeley.edu>
References: <0D.A2.21657.EFE7B834@pb1.pair.com>
	<01d801c5f46a$ac03d450$5c8be5a9@ohr.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Basic Namespace Requirements
From: jason@ionzoft.com (Jason Garber)

Hello Sara,

  Please explain what the difference is between nested classes, and
  this type of namespacing?

  If you scrapped namespace constants and functions, then all we have
  left is classes.  If it was looked at as nested classes, then we get
  all the functionality with all the simplicity and the benefit of
  being able to use "::".

  Please take a moment to explain, because I am an avid user, not a
  tokenizer :)

-- 
Best regards,
 Jason                            mailto:jason@ionzoft.com

Monday, November 28, 2005, 5:25:41 PM, you wrote:

>> 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).
>>
SG> Absolutely.  Static methods and Class constants are more than sufficient.
SG> All the added functionality of namespaces without all the baggage.

SG> +1

SG> -Sara