Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39589
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain at.wakwak.com designates 219.103.130.24 as permitted sender)
Message-ID: <489651F7.4070400@at.wakwak.com>
Date: Mon, 04 Aug 2008 09:48:55 +0900
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
Cc: internals@lists.php.net
References: <909776579.20080803142659@marcus-boerger.de>
In-Reply-To: <909776579.20080803142659@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Inconsistencies in 5.3
From: moriyoshi@at.wakwak.com (Moriyoshi Koizumi)

Fully agreed with all of those. (especially for 1)

Moriyoshi

Marcus Boerger wrote:
> Hello Internals,
> 
>   please let's not introduce new inconsistencies. Rather lets make new
> stuff consistent with old stuff during the alpha phase of 5.3.
> 
> 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
> 
> Best regards,
>  Marcus
> 
> 


-- 
Moriyoshi Koizumi <moriyoshi@at.wakwak.com>