CompositeCPPFunction is an index binding (see the comment at the top of CompositeIndexBinding). CPPFunction is a binding from AST. I don't know why isGloballyQualified is not implemented for most index bindings.
On Fri, Sep 26, 2008 at 12:19 PM, Thomas Ball
<tball@xxxxxxxxxx> wrote:
My refactoring needs to lookup a function declaration binding from a call to it, so it uses a NodeContainer.findAllNames() method to resolve the function call's name. The name's binding is a CompositeCPPFunction, but when the ExtractFunctionRefactoring runs the same code, it gets a CPPFunction for the same selection in the same file. I can't figure out what's different between the two refactorings (both lookups are done in checkInitialConditions(), so there hasn't been much setup yet). What is the difference between a CompositeCPPFunction and a CPPFunction? The difference matters because the PDOM support for CompositeCPPBinding.isGloballyQualified() isn't implemented.
Any help would be appreciated.
Tom
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
