Since this got cut without am answer I'll repeat it since *I* would still like
to know the answer!
Lester Caine wrote:
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?
If #3 is intended to work this way then it gets my vote.
Trying to apply namespace something substantial and understanding where the
code needs to be changed to work seems more logical than some of the academic
examples.
--
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
