Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33852
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sambarrow.com from 205.234.132.11 cause and error)
To: Robert Cummings <robert@interjinn.com>
Cc: Ken Stanley <dohpaz@gmail.com>, Lokrain <lokrain@gmail.com>,  internals@lists.php.net
In-Reply-To: <1197058210.14915.98.camel@blobule>
References: <alpine.DEB.0.98.0712042315260.20300@kossu.ez.no>
	 <475713B2.4030802@iamjochem.com> <475719ED.8050306@zend.com>
	 <200712052110.37023.larry@garfieldtech.com>
	 <47576AEF.4030306@omegavortex.net>
	 <5474E017-DF97-4B91-8FE0-7D6831E64F56@bitxtender.com>
	 <4EE0727E-ABBA-490D-B247-8C6E9A9727BA@gmx.net>
	 <E3.A1.00959.7AF49574@pb1.pair.com>
	 <345fd5cd0712070815k55eac42fh14d5685039c03113@mail.gmail.com>
	 <345fd5cd0712070816m2c0d4a22hd03f91abff2405ae@mail.gmail.com>
	 <c70e053d0712071157y56f7ba5bnabbcc4a47783a248@mail.gmail.com>
	 <1197058210.14915.98.camel@blobule>
Content-Type: text/plain
Date: Fri, 07 Dec 2007 15:55:32 -0500
Message-ID: <1197060932.28351.31.camel@sbarrow-desktop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Namespace
From: sam@sambarrow.com (Sam Barrow)

Very good point

namespace stuff ;
{
	function myfunction() {
		return true ;
	}
}

That would actually work, but it's not quite the same as you have the
semicolon after the namespace declaration, which looks kind of stupid.
Overall i dont think braces are a bad idea.

People say multiple namespaces per file are confusing, but braces would
partially solve this. If using braces makes multiple namespaces per file
more likely, I say that's the way to go, as I am very much in favor of
multiple namespaces per file.

On Fri, 2007-12-07 at 15:10 -0500, Robert Cummings wrote:
> On Fri, 2007-12-07 at 14:57 -0500, Ken Stanley wrote:
> > In regards to the braces or no braces question, I have a scenario that I
> > would like to share that could be considered similar in nature. We use a
> > cluster of databases where I work, and to make things easier on us, we have
> > a method called setSource() to switch between the clusters in our database
> > class. This allows us to easily query between the clusters, but since there
> > are no braces, we sometimes lose track of which cluster we are working on,
> > and thus bugs are born. I would think that if it were some how possible to
> > have braces, it would cause less headaches and problems, because we could
> > then logically group our queries together. The same argument could be used
> > with namespaces; especially _if_ the multiple namespace-per-file gets added.
> > Even without that little bit of functionality, it would make maintaining
> > namespaced code easier to read at first glance. For small apps, it probably
> > wouldn't be that big of a difference, but for files that span hundreds (and
> > even thousands) of lines of code, a developer could easily get lost in in
> > the namespace they are supposed to be in. Am I in a namespace? Which
> > namespace? Without the code block, and typical indentation, you could easily
> > overlook the namespace keyword.
> > 
> > Anyways, I understand that braces are just a bit of icing on the cake -- so
> > to speak -- but I just wanted to give a probable real-life situation to this
> > debate. :)
> 
> Is there any reason why you can't already use braces optionally? I mean,
> the following code is valid with the current engine:
> 
> <?php
> 
> {
>     {
>         {
>             class Foo
>             {
>                 function Foo()
>                 {
>                     echo 'Foo'."\n";
>                 }
>             }
>         }
>     }
> }
> 
> ?>
> 
> Cheers,
> Rob.
> -- 
> ...........................................................
> SwarmBuy.com - http://www.swarmbuy.com
> 
>     Leveraging the buying power of the masses!
> ...........................................................
>