LanguageController extension cache fails for system includes without extension

Milian Wolff mail at milianw.de
Mon Mar 21 17:43:49 UTC 2011


David Nolden, 21.03.2011:
> 2011/3/21 Milian Wolff <mail at milianw.de>:
> > David Nolden, 20.03.2011:
> >> I see no reason to rush on this. The "looking into files" behavior is a
> >> showstopper for really large projects (makes KDevelop unusable), while
> >> the other thing is just an annoyance.
> > 
> > No, KDevelop has not tons of files without extension. Only that part is
> > what I want to remove. Personally I find it much more a showstopper that
> > standard headers are not parsed correctly.
> > 
> >> There are a few things which we can do:
> >> - Allow looking into the file if it is open in the editor
> > 
> > most of the time you won't open a system header
> > 
> >> - Use the duchain to determine the language-support. If the file was
> >> ever included somewhere, there will be a TopDUContext for it.
> > 
> > no there wont. You create a parsejob for the include file but the
> > language controller will not find a language for it (as it has no
> > extension).
> 
> Yes there will. When you're including something, then the C++ support
> won't ask for its mimetype, and will simply parse it as C++.

re-reading this paragraph: if that would be the case, then this issue should 
not be encountered:

https://bugs.kde.org/show_bug.cgi?id=267877

or am I missing something? Maybe it's a different issue after all?

bye
-- 
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/20110321/99263e98/attachment.sig>


More information about the KDevelop-devel mailing list