Review Request: Do not perform background parsing when there are projects in state of loading
David Nolden
david.nolden.kde at art-master.de
Mon Feb 21 00:53:33 UTC 2011
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/100688/#review1542
-----------------------------------------------------------
You must not do something meaningful within Q_ASSERT(..), because that code will not be called in release mode.
Also, this probably breaks if the project-loading is aborted, right? You will probably have to listen to "projectClosed()", hopefully that one is emitted when the loading was aborted.
- David
On Feb. 19, 2011, 10:06 p.m., Dmitry Risenberg wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/100688/
> -----------------------------------------------------------
>
> (Updated Feb. 19, 2011, 10:06 p.m.)
>
>
> Review request for KDevelop.
>
>
> Summary
> -------
>
> In BackgroundParser, before running actual parsing, check whether there are projects in state of loading. If there are, wait until they are loaded completely. Without this, initially open files may be parsed two times: first as open files, second as members of a project. In the second case the list of include paths may be different, and that may cause some recursive re-parsing. Also differet sets of defines may cause re-parsing, though it wasn't tried.
>
>
> Diffs
> -----
>
> language/backgroundparser/backgroundparser.h a8a7b06
> language/backgroundparser/backgroundparser.cpp 28bdfee
>
> Diff: http://git.reviewboard.kde.org/r/100688/diff
>
>
> Testing
> -------
>
> Initial testing time varies greatly from launch to launch, so could not estimate the influence on average parsing time. However, the worst-case parsing time (when open files are parsed before their projects are loaded and then reparsed) does decrease.
>
>
> Thanks,
>
> Dmitry
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110221/29b378ee/attachment.html>
More information about the KDevelop-devel
mailing list