Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40117
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.134.190 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=rLD9d5kmwUVChJqWQQ2phDzN5BsW+UWZFCUbvcS+LQxVxmG9jC7m+IjpRF2dbdKKuf
         NyxHtEuswpr9eYRmG41v97rtoLwLHjIA6n0zEelfLTMqEqtz/v1qWtjAzr885VToBRiU
         eCrrVOoUKAM2adoXCnGKjzIU5sKN9E5ChQpqY=
Message-ID: <7f3ed2c30808272332m3066d1e5s677bb91f4b80c4b5@mail.gmail.com>
Date: Thu, 28 Aug 2008 08:32:46 +0200
To: "Felipe Pena" <felipensp@gmail.com>
Cc: "Marcus Boerger" <helly@php.net>, "Lukas Kahwe Smith" <mls@pooteeweet.org>, 
	"PHP Internals List" <internals@lists.php.net>, 
	"=?ISO-8859-1?Q?Johannes_Schl=FCter?=" <johannes@php.net>
In-Reply-To: <1219885057.5961.13.camel@pena>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <64B4CECA-980F-4738-8B05-E7935741D7BB@pooteeweet.org>
	 <E02EE232-938B-4E51-AB55-728C639642FD@pooteeweet.org>
	 <7f3ed2c30808271132x7443ea3gc4df903a3a2c73ec@mail.gmail.com>
	 <322434106.20080827234712@marcus-boerger.de>
	 <1219885057.5961.13.camel@pena>
Subject: Re: [PHP-DEV] alpha2 scheduled
From: hannes.magnusson@gmail.com ("Hannes Magnusson")

On Thu, Aug 28, 2008 at 02:57, Felipe Pena <felipensp@gmail.com> wrote:
> Hello Marcus,
>
> Em Qua, 2008-08-27 =E0s 23:47 +0200, Marcus Boerger escreveu:
>> Hello Hannes,
>>
>> Wednesday, August 27, 2008, 8:32:41 PM, you wrote:
>>
>> > On Tue, Aug 26, 2008 at 18:27, Lukas Kahwe Smith <mls@pooteeweet.org> =
wrote:
>> >> - Curly braces support for namespaces (Marcus, not ready for alpha2)
>>
>> > Why not? I thought I saw a patch for this on the list recently (which
>> > allowed both the current namespace foo; and namespace foo {}
>> > syntaxes)..
>>
>> It was an incomplete patch that simply allowed the syntax but did not
>> prevent code between two namespaces.
>
>
> That my old patch prevent the code between namespaces, but it only allow
> the syntax using { }. Then, I've updated it, now it allows both ({}, ;)
>
> Well, maybe it can be useful...
>
> Results using the patch:
>
> <?php
> namespace a {
> namespace b {
> }
> }
> Fatal error: Nested namespace is not allowed in %s on line %d

I'm really sorry, but I have to ask.
Since you can detect that this is a nested namespace, why can't we allow it=
?
namespace foo {
  class one {}
  namespace bar {
    class two {}
  }
}

becomes class foo::one and class foo::bar::two ?

-Hannes