Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39649
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 76.96.30.64 cause and error)
To: internals@lists.php.net
Date: Mon, 4 Aug 2008 22:42:16 -0500
User-Agent: KMail/1.9.9
References: <909776579.20080803142659@marcus-boerger.de> <4896BDB3.7000003@e-novative.de> <698DE66518E7CA45812BD18E807866CE01DAD465@us-ex1.zend.net>
In-Reply-To: <698DE66518E7CA45812BD18E807866CE01DAD465@us-ex1.zend.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200808042242.16962.larry@garfieldtech.com>
Subject: Re: [PHP-DEV] Inconsistencies in 5.3
From: larry@garfieldtech.com (Larry Garfield)

On Monday 04 August 2008 10:29:33 am Andi Gutmans wrote:

> Re: braces, I don't think it's a big deal but I would prefer without
> braces. Given that I think people should only have one namespace per file,
> the braces is a PITA because it already starts you off in an additional
> layer of indentation. We all know that whitespace does matter :) Also
> another reason to not have braces because then it then makes sure that you
> don't go back into a global namespace and it is truly only used in these
> framework concatenation use cases.

There's always 

class Foo::Bar { ... }

if you want to avoid too much indentation. :-)

*runs*

Seriously though, the main problem I see with the non-braces mechanism is 
that, as others have observed, it is the only place in PHP (AFAIK) where file 
matters.  All other code can be shuffled about from file to file without 
breaking.  That's rather inconsistent.

-- 
Larry Garfield
larry@garfieldtech.com