Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:36340
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.163 as permitted sender)
To: Marcus Boerger <helly@php.net>
Cc: internals@lists.php.net
In-Reply-To: <1789567073.20080321223647@marcus-boerger.de>
References: <1789567073.20080321223647@marcus-boerger.de>
Content-Type: text/plain
Date: Sat, 22 Mar 2008 22:32:30 +0100
Message-ID: <1206221550.31721.4.camel@goldfinger>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] Namespace syntax decision
From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

On Fri, 2008-03-21 at 22:36 +0100, Marcus Boerger wrote:
> PHP is very close to Java and C++ in terms of Syntax. And many of our users
> are familiar with one or even both of them. Also we have a tendency to
> especially take syntax from those two or be in line with those two
> languages. That said I see two ways:
> 
> 1) namespace foo { }
> 
> 2) package foo;
> 
> I favor 1) if we allow namespace nesting and 2) if not. The current way of
> nesting is very confusing:
> namespace foo; namespace bar;

I said in some previous post I won't like multiple namespaces per file
using the 2nd syntax. So imo: either on ns per file and the 2nd syntax
or allow multiple and use brackets. And then I prefer the latter.

johannes