Thread-safety issue in cmake support ?

Milian Wolff mail at milianw.de
Sun Jun 13 14:13:36 UTC 2010


On Sunday 13 June 2010 16:09:47 David Nolden wrote:
> 2010/6/12 David Nolden <zwabel at googlemail.com>:
> > 2010/6/12 Milian Wolff <mail at milianw.de>:
> >> David Nolden, 12.06.2010:
> >> well, what you show up there is just what we proposed, only slightly
> >> different. You copy the editor contents in the ::run() method, while
> >> we'd do it before its done, i.e. directly in the foreground thread.
> 
> One more related problem which makes the foreground lock the simpler
> way: We cannot do all the foreground stuff in the constructor of the
> parse-job, because additional parse-jobs are created locally from
> within the backgruond for the #included files (which we only know
> after preprocessing), and those also may require access to the
> foreground for editor-text-retrieval, highlighting, etc.
> 
> Btw. I am working on porting the DUChain away from smart-ranges just now.

YYYYYYEEAAAAAAAAAAAAHHHHHHHH :) :)

Thank you _so_ much David!!!
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100613/8eee0103/attachment.sig>


More information about the KDevelop-devel mailing list