Namespace constants can be handy if you'd want to include some library
that uses predefined constants and classes that might conflict with
other classes and constants in the script.
namespace someLib {
include('huge_conflicting_library_that_I_dont_want_to_reverse_engineer');
}
Stanislav Malyshev wrote:
MB>> your patch wasn't complete. There are conflicts as soon as you have
MB>>subnamespaces or constsants.
You mean namespace contsants? I don't think they are needed. You can
always define utility class for them if you want. As for subnamespaces,
which I think also not necessary anyway, I don't see any problem there.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
