KDE/kdevelop/plugins/languages/cpp
Alex Merry
kde at randomguy3.me.uk
Mon Jan 5 00:15:12 UTC 2009
On Sunday 04 January 2009 23:51:18 David Nolden wrote:
> Am Monday 05 January 2009 00:42:56 schrieb Andreas Pakulat:
> > This sounds like the wrong fix. C++ plugin shouldn't be loaded by
> > default, only on demand when actually opening a C++ file, right David?
> >
> > Could be a bug in the plugin-loading logic in
> > PluginController::initialize()
That could be the case - I didn't do anything apart from open KDevelop (first
run, so no session restored) and close it again. I wouldn't expect this to
load the C++ support plugin.
>
> It might be loaded when the class-browser or something similar requests to
> laod some C++ duchain objects, and if it happens in foreground, this will
> trigger a loading of the language support.
>
> Even if class-view is fixed, we would still have to live with this.
Unless you can guarantee that a Language object is created for "C++" and added
to the LanguageController every time the C++ language support plugin is
loaded, I would have thought the guard I added needs to be there.
Actually, I can't quite see why CppLanguageSupport::language() returns 0
rather than going into an infinite loop, since it calls core()-
>languageController()->language("C++"), and
LanguageController::language(QString) seems to call
ILanguageSupport::language() (presumeably CppLanguageSupport::language() in
this case) if it can't find a cached Language object.
Alex
-------------- 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/20090105/ab6908ec/attachment.sig>
More information about the KDevelop-devel
mailing list