[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 218261] Kdevelop is unusable (too slow) when project is stored
From:       Maciej Cencora <m.cencora () gmail ! com>
Date:       2009-12-12 0:22:05
Message-ID: 20091212002205.EC5C32B790 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=218261





--- Comment #5 from Maciej Cencora <m cencora gmail com>  2009-12-12 01:22:04 ---
(In reply to comment #4)
> Whenever reparsing a file, kdevelop has to check whether any of its hundreds of
> includes has changed. And if it decides to reparse a file, then it has to
> search for all "#include"ed files within all include-paths.
> 
> Both of these are probably the reason why it is so slow on your remote
> filesystem. There is not much that can be done here, as both of these steps are
> required. The filesystem could do some caching to speed it up.

I don't see a reason why you'll want to reread all includes every time. 
I think it can solved pretty easily:
Let's say we have some source and header files open. When we update the header
files, just schedule reparsing of all other open files (or only files that
depend on currently edited header if it's possible) - start reparsing when user
switches tab to other file.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]