Jump to definition doesn't work with overloaded functions
kitts
kitts.mailinglists at gmail.com
Thu Mar 1 03:49:24 UTC 2007
On Thursday 01 Mar 2007 IST, Andreas Pakulat wrote:
> After talking to Kris Wong a bit, it seems the code-completion is to
> blame. For this particular case it would be enough if the codemodel
> would know how many arguments a function takes and which ones have
> default values. Probably the same for a given function call. Then the
> above case where the two overloads have a different number of arguments
> should be solved.
>
> It would certainly nice if kdevelop used type information to find the
> right overload so cases like
>
> void foobar( int i1, char* c1);
> void foobar( bool b1, char* c2);
>
> would work when the code looks like
>
> foobar(getInt(),getChar());
>
> But Kris already told me that this would probably be too time-consuming.
> Still this is something kdev4 should make possible.
Sorry for holding up this thread but i have a question...
Would it be possible in future that if the file has been compiled and
linked, the various jumps jump to the locations that the compiler/linker
saw rather than whats identified by the KDevelop's parser?
--
Cheers!
kitts
More information about the KDevelop-devel
mailing list