Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32277
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 204.127.200.83 cause and error)
To: 'PHP Internals' <internals@lists.php.net>
Date: Tue, 11 Sep 2007 20:40:10 -0500
User-Agent: KMail/1.9.6
References: <46E5D163.4050800@zend.com> <1869442285.20070911113436@marcus-boerger.de>
In-Reply-To: <1869442285.20070911113436@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-ID: <200709112040.10581.larry@garfieldtech.com>
Subject: Re: [PHP-DEV] multiple namespace per file
From: larry@garfieldtech.com (Larry Garfield)

On Tuesday 11 September 2007, Marcus Boerger wrote:
> Hello Stanislav,
>
> Tuesday, September 11, 2007, 1:21:07 AM, you wrote:
> > Hi!
> >
> > Following the feedback from the community, we (mostly me and Dmitry)
> > tried to find a good model that would allow multiple namespaces per file
> > without running into too many problems and complications, and would
> > allow to bundle multiple namespaced files together without
> > modifications. It looks like it is possible to do, but only under the
> > following condition: the file can have multiple namespaces, but if the
> > file has namespaces, then it can have no code outside namespaces.
> >
> > For example, this would work:
> > namespace A;
> > class X {}
> > namespace B;
> > class Y {}
>
> This looks very messy. We should either go with curly braces or with one
> namespace at the top of a file. And even if we do multiple namespaces per
> file. I guess we do not allow a naespace to be spread onto several files,
> right?

=46rom a readability-usability perspective (which is all I am able to offer=
),=20
I'd have to agree with Marcus.  The syntax should follow the structure of t=
he=20
parser.  So either:

<?php // One namespace per file only
namespace Foo;
class X {}
function bar() {}
?>

or=20

<?php // Multiple namespaces permitted
namespace Foo {
  class X {}
}

namespace Baz {
  function bar() {}
}

I agree that allowing stuff in a file outside of a namespace if namespaces =
are=20
used would be all kinds of confusing with either syntax.

=2D-=20
Larry Garfield			AIM: LOLG42
larry@garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of=20
exclusive property, it is the action of the thinking power called an idea,=
=20
which an individual may exclusively possess as long as he keeps it to=20
himself; but the moment it is divulged, it forces itself into the possessio=
n=20
of every one, and the receiver cannot dispossess himself of it."  -- Thomas=
=20
Jefferson