Hi! > keep in mind those 20 bits that are different in every file!". But after > delocalizing it, all hope is lost - you never know what the code in the > file actually means - because somebody could write code in completely > different file, maybe even JSON composer configuration or some other > config file you didn't even think to be able to change your language > semantics - and suddenly all the code works differently.
Oh, I missed even worse feature - if you have namespace A\B\C, then you get shared semantic context not only from this namespace, but also from \A and \A\B. Which means basically that finding what semantic context you end up with becomes several times harder - you need to locate not only who may be controlling your namespace's context, but who is controlling contexts of all the parent ones. And each time a new semantic fork is introduced, you'd scan the whole tree and ensure every node on the way agrees on which side of the fork they are, or explicitly define it if you don't want to rely on all the parent chain always staying on the same side you are. -- Stas Malyshev [email protected] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
