Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41111
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.123 cause and error)
Message-ID: <48F6E50E.4010107@lsces.co.uk>
Date: Thu, 16 Oct 2008 07:54:06 +0100
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: <48F6B3C5.9030102@chiaraquartet.net> <7f3ed2c30810152312h5391b25dke2695362c8d28d3b@mail.gmail.com>
In-Reply-To: <7f3ed2c30810152312h5391b25dke2695362c8d28d3b@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] namespaces sanity: addition to RFC explaining why Stas's
 proposal doesn't work
From: lester@lsces.co.uk (Lester Caine)

Hannes Magnusson wrote:
>> I was asked to explain why I hadn't included ClassName->Method(); in the
>> list of ideas that solve the ambiguity problem.  I added a brief section
> 
> Can we please start small and then incrementally add more features?
> Lets start with classes only in namespaces in 5.3.

The problem with that statement is that if it is used to ignore the other 
problems, then at some point it may be necessary to re-write all the new 
namespace code simply to allow additional features to be added!

While I think it would be NICE to see a different separator, ':::' seems to 
annoy people, and using something else may cause problems for people with 
'non-standard' keyboards who have trouble with some characters already?

So 'USE' ?
I'm I understanding things right on this one that one would 'define' the 
namespace in one sort of header file, and then add the use namespace to those 
files that build on the basic definition? I'm looking in particular here at a 
library like ADOdb, where 'adodb.inc.php' has a number of global functions 
which are then used by the various drivers. So 'adodb.inc.php' would define 
'ADOdb' as a namespace and each driver would
'use namespace ADOdb'

This seems a good example to work with and is the reason that simply dropping 
functions rang alarm bells with me. In fact it was the Date stuff from ADOdb 
that caused so much trouble with 'Date' in earlier releases so it seems 
appropriate to investigate how namespace would work with it? There are 
obviously other ways the problem could be solved, but a simply wrapper is the 
right approach initially?

Or am I barking up the wrong tree?

-- 
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