Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31842
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain interjinn.com from 66.11.173.122 cause and error)
To: Lukas Kahwe Smith <mls@pooteeweet.org>
Cc: Marcus Boerger <helly@php.net>, Rasmus Lerdorf <rasmus@lerdorf.com>,  Stanislav Malyshev <stas@zend.com>, internals Mailing List <internals@lists.php.net>
In-Reply-To: <46CC4503.7000407@pooteeweet.org>
References: <46C9F217.8040804@chiaraquartet.net>
	 <000001c7e3cb$9a80b160$6e02a8c0@thinkpad>
	 <1925889548.20070821122333@marcus-boerger.de>  <46CB1E05.4090100@zend.com>
	 <bcb7aa500708211206i9a7b29cp5a330add726e28cd@mail.gmail.com>
	 <46CBCDC7.1040001@lerdorf.com> <591963703.20070822135708@marcus-boerger.de>
	 <1187791987.10256.73.camel@blobule>  <46CC4503.7000407@pooteeweet.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: InterJinn
Date: Wed, 22 Aug 2007 10:17:41 -0400
Message-ID: <1187792261.10256.75.camel@blobule>
Mime-Version: 1.0
Subject: Re: [PHP-DEV] [PATCH] allowing multiple namespaces per file plus
	namespaces with brackets
From: robert@interjinn.com (Robert Cummings)

On Wed, 2007-08-22 at 16:15 +0200, Lukas Kahwe Smith wrote:
> Robert Cummings wrote:
> > On Wed, 2007-08-22 at 13:57 +0200, Marcus Boerger wrote:
> >> Hello Rasmus,
> >>
> >>    the limitations given here and very good explained should imo stay. They
> >> should because that is not only easier to understand and easier for anything
> >> that has to deal with it like opcode caches and whatnot but also adhrers to
> >> the good old KISS approach of PHP.
> >>
> >> That said, instead of changing the current implementation every day we
> >> should step back a bit and first find a consensus whether we want anything
> >> more or even anything less than what we currently have.
> >>
> >> My personal feeling is that we should stick to one name binding per file.
> >> And we should do so without braces (if I want it complex I just take a more
> >> complex language).
> > 
> > While I agree with the one namespace per file camp I think your above
> > argument "if I want it complex I just take a more complex language" is
> > akin to saying "If I want it OOP I'll take a more OOP language". I'm
> > sure you'll agree that's not a very good argument.
> 
> Make as much hard but common stuff easy, keep the easy stuff easy and 
> make the hard stuff possible. Could this be our mantra?

It's a great mantra, just not always possible :)

Cheers,
Rob.
-- 
...........................................................
SwarmBuy.com - http://www.swarmbuy.com

    Leveraging the buying power of the masses!
...........................................................