Bug 315505 - Overly eager trying to auto-include graph_concepts.hpp (and other boost includes)
Summary: Overly eager trying to auto-include graph_concepts.hpp (and other boost inclu...
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
: 326167 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-02-20 10:48 UTC by Kevin Funk
Modified: 2015-11-30 17:12 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Image describing the issue (159.05 KB, image/png)
2013-02-20 10:49 UTC, Kevin Funk 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Funk 2013-02-20 10:48:26 UTC 
When boost includes have been parsed, you always get a hint to include "graph_concepts.cpp" in case of typing a single-letter in files.

Attached screenshot explains the issue.

Easy to reproduce when the VTK project is loaded, which uses boost.



Reproducible: Always



Expected Results:  
Maybe don't give hints for single-letter strings?
Comment 1 Kevin Funk 2013-02-20 10:49:22 UTC 
Created attachment 77452 [details]
Image describing the issue
Comment 2 Kevin Funk 2013-02-20 12:41:05 UTC 
The root problems seems to lie in http://www.boost.org/doc/libs/1_52_0/boost/concept/detail/concept_def.hpp

KDevelop fails to parse the BOOST_concept macro, hence the code in http://www.boost.org/doc/libs/1_52_0/boost/graph/graph_concepts.hpp using these macros are not expanded properly.

Types such as "typename graph_traits<G>::vertex_descriptor u, v;" end up in the wrong namespace.
Comment 3 Kevin Funk 2013-10-18 06:22:15 UTC 
*** Bug 326167 has been marked as a duplicate of this bug. ***
Comment 4 Kevin Funk 2015-11-27 19:37:28 UTC 
I think we've fixed that at some point. Can't reproduce. Can anyone else?
Comment 5 rjwgnr27 2015-11-30 17:12:32 UTC 
(In reply to Kevin Funk from comment #4)
> I think we've fixed that at some point. Can't reproduce. Can anyone else?

I have not seen this in some time. I would say it's fixed.