Hello,
Well, I wouldn't use the include_path parameter of PHP for the new
namespaces lookup code, neither __autoload(). I see it as a major
language change -- the support of namespaces, where you should consider
to make all need. I suppose you want to support namespace spread over
multiple files, this shouldn't be a problem. I would only drop the
support of one class spread over multiple files for only one namespace,
nice time to raise a Fatal Error/compiler error.
You could support nameless namespaces (i.e. namespace {}) and for
backward compatibility sake dump all "float" methods in this nameless
namespace, won't cause problem. And all "new code" should just
namespaces by default, if not it will be jumped into the nameless
namespace. For example when you call a function like myNameRocks() it
should just look for the function in the nameless namespace and go with
it. Not existing? Bang! Function doesn't exist.
Enough dreaming for now, time to work again :-)
--
Yours,
Weyert de Boer ([EMAIL PROTECTED])
innerfuse*
http://www.innerfuse.biz/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
