why must a NamespaceAliasDeclaration's importIdentifier not be explicitlyGlobal?

[Milian Wolff]

Ok, I break my promise, yet another email today to you David ;-)

https://bugs.kde.org/show_bug.cgi?id=263532

PHP plugin can assert when someone writes something like this:

<?php
use \some\context;
?>

which is essentially the same as in cpp:

using namespace ::some::context;

Why is it forbidden to have a identifier with explicitlyGlobal set? What's 
wrong with that? In cpp lang plugin I see in 
DeclarationBuilder::resolveNamespaceIdentifier that you remove this flag. But 
I would know *why*? This is quite unexpected, even though it's documented. 
Could the explicitly global not get removed in 
NamespaceAliasDeclaration::setImportIdentifier?

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110118/4eaa46a0/attachment.sig>