Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41481
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.184 cause and error)
Message-ID: <4906168C.7060900@lsces.co.uk>
Date: Mon, 27 Oct 2008 19:29:16 +0000
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <d1bff87d0810260351n4361e42n62b86165ef56c70@mail.gmail.com>	 <49047D62.1030900@lsces.co.uk> <49059FC1.2060702@vector-seven.com>	 <9b3df6a50810270411t2b8e050au33d68564225311d4@mail.gmail.com>	 <4905A81F.3070506@vector-seven.com>	 <20081027121602.GY30862@mint.phcomp.co.uk>	 <d1bff87d0810270529j39b4ec16j3e7e0cfecfc112ce@mail.gmail.com> <261daaa10810270552s954e580u3151a3c2002343db@mail.gmail.com>
In-Reply-To: <261daaa10810270552s954e580u3151a3c2002343db@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RE: </endnamespacediscussion>
From: lester@lsces.co.uk (Lester Caine)

Vesselin Kenashkov wrote:
> 1. One user of namespaced constants & functions here... I dont like to use
> objects for everything. I have very few constants & functions but I would
> like them to remain constants & functions instead of converting them to
> static classes or object methods.
> 2. One reason against dropping ns for functions & constants is that if you
> drop them how you can namespace legacy (or to avoid that word, not OOP)
> code? This way many libraries can not be namespaced and if you have a name
> collision you will not be able to solve it using namespaces.
> 3. I prefer using\name\spaces instead of prefixing_my_classes. Here is why -
> I want to organize my files in a hierarchical way in the file structure. A
> possible solution withtout namespace using prefixes couldbe
> level1_level2_classname (spliting the name by _). But if I want it to be
> class_name? Then I have an confusion. And I personaly dislike camelCase and
> level1_level2_className does not works for me.
> Because of this I prefer to have namespaces instead of class prefixes. Then
> I can do name\space\class_name.
> 4. When you have namespace you can short_the_long_class_name used multiple
> times in your code importing the namespace and then using the 'shortcut'.
> 
> I put the last two just to explain why I prefer to have namespace with
> whatever by separator instead of dropping them.

I'm with you on that Vesselin. Will I use namespace - probably not, but I can 
see straight away blocks of code in projects I'm involved with that require 
functions at least in the namespace. SO they should be re-written? Probably, 
but one of the tidiest ways of handling even that is to wrap the legacy code 
in it's own namespace. If functions and constants were dropped simply to push 
an incomplete solution through, then it would cause a lot more trouble than 
the current flack. The result is not 'ideal' but it is perfectly functional 
and from what I've seen so far WILL work with legacy code.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php