SmartRange revisions in ParseJobs

[Milian Wolff]

Hey all, esp. David:

With recent trunk you'll see that Cristoph added a warning when the 
clearRevision is called from the wrong thread (the locks are apparently per-
thread else all kind of havoc could happen).

The parsejobs do useRevision in contentsAvailableFromEditor but clearRevision 
in their dtor, both are in different threads (form in the background due to 
backgroundparser, latter somewhere else due to signal/slot connections).

So how should we fix that properly in KDevelop? Introduce something like a 
SmartRevisionLocker that does clearRevision when it gets closed down, and set 
this up in the ::run() of each ParseJob? I can't see how it could be 
completely hidden from the implementation of a language parsejob though...

Ideas?
-- 
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: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100219/08165080/attachment.sig>