Version: 3.9.96 (using KDevPlatform 0.9.96) (using 4.3.3 (KDE 4.3.3), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.29-gentoo-r5 Use some sort of persistent storage for code browser database to speed up loading when opening a project (parse only changed files) Right now code browser parses every time and i work on something like 86MB of source code which is parsed in a few minutes. I almost never parse whole project because takes too long and if kdevelop crashes its bye bye database anyway.
We already use a persistent storage. The problem is that crashes can make this storage invalid and hence it has to be cleared. The more stable kdevelop becomes, the less you'll have to reparse.
Strictly speaking, kdevelop could have used something like Berkely DB to avoid db corruption in such situations ...
@Vadym Krevs: That doesn't make sense, given the amount of information we store in the duchain, any kind of 'stable' database storage would be horribly slow, and also complete overkill, as the information is not 'valuable' at all, it's just a cache. Just keep reporting your crashes, then KDevelop will become more stable, and the database won't be cleared that often. Parsing performance is worked on as well.