Completion quirks

Andreas Pakulat apaku at
Sun Jul 8 22:03:16 UTC 2007

On 08.07.07 14:22:35, Yang wrote:
> I'm using KDevelop 3.4.0 and I find that completion suggestions are
> incorrect (incomplete). For instance, when I do:
> ifstream in("blah");
> in.
> Here, the completion lists only a few of basic_ifstream's members, and
> not (for instance) read. Is this a limitation of the current
> parser/indexer?

Probably the parser, especially if typedef's are involved.


Are you a turtle?

More information about the KDevelop mailing list