Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39829
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
To: Marcus Boerger <helly@php.net>
In-Reply-To: <909776579.20080803142659@marcus-boerger.de>
References: <909776579.20080803142659@marcus-boerger.de>
Message-ID: <840985F2-A701-4BE4-91F6-F6B39048CF9B@pooteeweet.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Mon, 11 Aug 2008 12:34:00 +0200
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Inconsistencies in 5.3
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 03.08.2008, at 14:26, Marcus Boerger wrote:

> 1) new keyword 'use'. Semantically it is the same as 'static' or  
> 'global'
> so it should be used in the same location.
>
> 2) namespaces, either use 'package' and only one per file, or use
> 'namespace' with curly braces. Read this as be consistent with other
> languages and even if one or two people do not like it the two main
> languages out there which have it are Java which goes with the  
> former and
> C++ which does the latter. Please chose and not mix it. Also our mix  
> is a
> nightmare when developing code.
>
> If we feel we have to keep the keyword 'namesapce' but cannot have  
> curly
> braces, than I suggest we disallow multiple namespace per file.
>
> And there is no technical reason and surely no other reason  
> whatsoever to
> not have curly braces. If there is then we either fix that or went  
> with the
> wrong approach.
>
> 3) __invokable, see Etiene's mail


AFAIK 3) is resolved?

So it seems to me like 1) and 2) have gone back and forth between  
people enough. We have also agreed that multiple namespaces per file  
are a necessary feature to support. But now the question is if we are  
going to change anything or not.

Ideally someone would summarize the discussion (or maybe two people,  
one from each "camp") and then we can have a vote. Make it an RFC or  
whatever. But this is definitely the last time we are going to vote on  
the curly brackets stuff for namespaces in 5.3.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org