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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
