Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40486
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.46.28 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:mime-version:content-type
         :content-transfer-encoding:content-disposition;
        b=EHMxYjw93tMKF6Pv5T5/et+50nTZV1ZKvUwaq40wdk7wzTA7btqL8cyed5CEmYDKyJ
         2MFCga50ivl2Tsqwxw+oKYq7+LflPecW6Nq2zbtttNN8yzQ4sPhpMw9CrK7LndeLlUO5
         A0gMLTGNnY/2oKNkgk2oz02Nrz4mnjgJYaWRs=
Message-ID: <afabb7690809121335x58a521eeq7a3aef8ea529e50d@mail.gmail.com>
Date: Fri, 12 Sep 2008 17:35:24 -0300
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: the namespace war
From: domluc@gmail.com ("Lucas Stephanou")

So, after this msg(my second on list) maybe  you will scream with me, but.

This namespace war is putting you focus on a great feature, but maybe
losing time with lot of discussion.

namespace foo;
or
namespace foo{
(...)
}

are both good options, but can we stop the war and go forward, as php
user I was losing with this fight.

My opinion is that
namespace foo{}

is best for all, some cache systems that rely on concat files maybe
will break with namespace; option


ps.: sorry for breaking this discussion on the middle

-- 
Lucas Stephanou