LanguagePlugins and AlwaysOn

[David Nolden]

Simply use the foreground lock. It's the same as andreas's "queue approach,
but only with 1 LOC.

We can then change the check in languageForUrl to VERIFY_FOREGROUND_LOCKED ,
and have one less ugly multi-threading problem. I also always thought that
it sucks not being able to load plugins from the background.

Am 17.06.2010 21:43 schrieb "Milian Wolff" <mail at milianw.de>:

On Thursday 17 June 2010 19:56:44 Andreas Pakulat wrote:
> On 17.06.10 19:10:47, Milian Wolff wrote:...
I explicitly wanted to prevent that. What I have now is much easier since I
can just build a context of a different language without having to create a
new
parse job for that, which would end up in the parse queue waiting...


-- 
Milian Wolff
mail at milianw.de
http://milianw.de

--
KDevelop-devel mailing list
KDevelop-devel at kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100617/50452f48/attachment.html>