Some DUChain related questions
svenbrauch at googlemail.com
Fri Nov 12 23:46:24 UTC 2010
Thanks for your answers, by debugging that function I now found the problem
(or well, five of them): context ranges weren't set correctly, i.e. classes
and functions randomly ended on the line where they started.
2010/11/10 Milian Wolff <mail at milianw.de>
> David Nolden, 09.11.2010:
> > 2010/11/9 Sven Brauch <svenbrauch at googlemail.com>:
> > > usebuilder source code:
> > >
> > > .cpp As can be seen in the second image, declarations from the class
> > > context are imported into the function. This is not correct for python.
> > > I already removed the statement of which I thought would do that, but
> > > nothing changed. What to do here? The contextbuilder code:
> > >
> > > lder.cpp#L213 My UseBuilder.buildUses() calls functions from the
> > > contextbuilder. Is that
> > > correct? Looks very strange to me, as this is a seperate build pass.
> > Unfortunately, all the builders inherit each other (at least in C++),
> > which creates a slightly hard to overview code-flow. It should be fine
> > for the use-builder to call context-builder functions, as the
> > use-builder is run in a second pass, and is 'driven' by the
> > context-builder which traverses the AST and duchain hierarchy
> > synchronously.
> see also: compilingContexts() in abstract context builder
> Milian Wolff
> mail at milianw.de
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel