Gathering the set of files-to-watch

David Nolden zwabel at
Sat Jun 12 21:11:09 UTC 2010

2010/6/12 Esben Mose Hansen <kde at>:
> On Saturday 12 June 2010 21:59:26 Milian Wolff wrote:
> Thanks for all the answers :) David, too, of course.
>> Assuming that file was already parsed once you should check the features of
>> that existing version and reuse them. Otherwise use the default which would
>> be without uses and ast afaik. AST is definitely not required by default.
> Ok. Wouldn't usages be wrong or outdated, then? I do those get rebuild as
> needed? But redoing with the same level sounds like the *intelligent* thing to
> do. Where should I look for that information?

No you simply shouldn't care about this. The background-parser and the
parse-jobs will figure out the right thing to do, you should just give
them the lowest features that you want, which is

>> > My next item on the list is getting and watching the includes of a file.
>> > The cleanup, and finally I'll submit it to the mercy of the core
>> > developers :)
>> I'm interested in it. How many watchers do you setup now for a medium sized
>> project? E.g. kdevplatform + kdevelop?
> 191 (directories, file watches are useless for these purposes)
> I expect this to rise somewhat once I get the included files, especially for
> Qt projects (as they tend to have included files in every build dir, too).
> Still, I think the limit is about 8K directories, so there is some headroom
> still.

I hope the watches won't be a too hard hit on the performance.

Greetings, David

More information about the KDevelop-devel mailing list