Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31636
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain smashlabs.com from 67.15.58.61 cause and error)
Message-ID: <46C4964A.4070302@smashlabs.com>
Date: Thu, 16 Aug 2007 13:24:10 -0500
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC: Marcus Boerger <helly@php.net>, 
 'PHP Internals' <internals@lists.php.net>
References: <46BE14B1.5050209@zend.com> <101178402.20070814174515@marcus-boerger.de> <46C1EB6C.8000601@zend.com>
In-Reply-To: <46C1EB6C.8000601@zend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Fwd: Re: [PHP-DEV] Renaming namespaces to packages]
From: ralph@smashlabs.com (Ralph Schindler)

Stas,
   Namespace implementations for languages have been around for decades 
in one form or another.  People use the languages they are used to 
developing in to demonstrate their points on how it should work, and 
what it should be called when it works a certain way. Its 2007. Given 
that we have the benefit of seeing how other languages have attempted to 
solve the problem over the years, we can then devise our own 
implementation to satisfy the demand.  We cannot ignore other languages 
implementations that got us to where we are today in language/compiler 
design.

At the end of the day, there are two camps of people for naming: 
packages vs. namespaces.

You seem to be missing the point that having braces is not for vanity's 
sake, and is truly important to the implementation thus lending itself 
to actual naming of the implementation.

a) BY NOT HAVING BRACES you have subscribed to FILE BASED scope 
termination, thus tying the SCOPING of namespaces to a FILE.

b) BY HAVING BRACES you would be subscribing to a model that terminates 
scope of namespace constructs to current scope they are defined within.

The former lends itself to being called a "package" the later lends 
itself to being called a "namespace".

You did not answer my other questions on multiple namespaces per file, 
and interactive php namespace usage.

-ralph



Stanislav Malyshev wrote:
>> OO. And anyway, are we struggling to find excuses here? Can we in no way
>> ever at least try to be consistent in anything we do? That JS argument 
>> is an
> 
> How "consistent" had acquired a meaning of "doing it my way"? There's 
> nothing inconsistent in the name "namespace" and it is very consistent 
> with what people understand - I quoted wiki on that. I'm still waiting 
> for that non-"C++ does it with braces" argument btw.