Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39607 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90340 invoked from network); 4 Aug 2008 08:45:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Aug 2008 08:45:25 -0000 Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Linux 2.6 Received: from [85.214.94.56] ([85.214.94.56:45789] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5B/88-46562-5A1C6984 for ; Mon, 04 Aug 2008 04:45:25 -0400 Received: from MBOERGER-ZRH.corp.google.com (176-81.106-92.cust.bluewin.ch [92.106.81.176]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id BC1D811DDE5; Mon, 4 Aug 2008 10:45:22 +0200 (CEST) Date: Mon, 4 Aug 2008 10:42:33 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <4110083360.20080804104233@marcus-boerger.de> To: Dmitry Stogov CC: internals@lists.php.net In-Reply-To: <4896A7C4.8090503@zend.com> References: <909776579.20080803142659@marcus-boerger.de> <4896A7C4.8090503@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Inconsistencies in 5.3 From: helly@php.net (Marcus Boerger) Hello Dmitry, Monday, August 4, 2008, 8:55:00 AM, you wrote: > Hi Marcus, > see below > 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. > For me 'use' is the best keyword as it says that closure uses variables > from current content. (the same keyword is used for import from namespaces) To be clear, I wasn't complaining about the keyword per se. I just prefer it to be inside the curly braces of a closure next to global rather than in front of it. >> 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. > I don't like multiple namespaces per file too. > As I remember they were introduced by Greg's request related to > ext/phar. May be he already changed his mind. > 'package' or 'namespace' is not so important for me. > Thanks. Dmitry. >> 3) __invokable, see Etiene's mail >> >> Best regards, >> Marcus >> >> Best regards, Marcus