Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33696
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain dealnews.com designates 129.41.69.137 as permitted sender)
Message-ID: <4755D720.4040003@dealnews.com>
Date: Tue, 04 Dec 2007 16:39:28 -0600
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Derick Rethans <derick@php.net>
CC: PHP Developers Mailing List <internals@lists.php.net>
References: <alpine.DEB.0.98.0712042315260.20300@kossu.ez.no>
In-Reply-To: <alpine.DEB.0.98.0712042315260.20300@kossu.ez.no>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Dropping Namespace
From: brianm@dealnews.com (Brian Moon)

> With all the above considerations, especially my first point, I still have not
> heard any good reason why namespaces in the current implementation are actually
> useful - or what particular case they solve... so I am wondering, are they
> really useful? I come now to the conclusion that they are not, and for myself
> (and most likely my work projects) I would have to decide not to go with
> namespaces, but instead stick with the 3 letter prefixing.  Something that I
> have totally no problem with, as it is nice and easy.

I hate to, but I agree.  If the only point is to make class naming 
pretty, it is kind of pointless.  Give me namespaces that scope 
variables to a file and then we have something.  Yeah, I still code the 
way PHP intended you to code, by templateing files together and not 
making gynormous classes to print out some simple HTML over and over.

It would only be useful in that my company's code would not conflict 
with some 3rd party software we use.

-- 

Brian Moon
Senior Developer
------------------------------
http://dealnews.com/
It's good to be cheap =)