Bug 321075 - KDEvelop can't parse for new c++11 for loop over literal lists
Summary: KDEvelop can't parse for new c++11 for loop over literal lists
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: git master
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-12 20:09 UTC by Leandro Santiago da Silva
Modified: 2016-09-08 20:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 5.0.0
Sentry Crash Report:


Attachments
some test cases (486 bytes, text/x-csrc)
2013-06-12 20:10 UTC, Leandro Santiago da Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leandro Santiago da Silva 2013-06-12 20:09:20 UTC
The new c++0x introduces embraced list support {v1,v2,v2} which is currently supported in kdevelop, but not inside a for loop.

Something like for (int i: {1,2,3,4}) isn't recognized by the parser.

I've attached an .cpp file I used as an example of code.



Reproducible: Always

Steps to Reproduce:
Open the attached code in kdevelop.
Actual Results:  
The text editor show lots of errors arround the list "{}" and don't know the name of the loop iterator.
Comment 1 Leandro Santiago da Silva 2013-06-12 20:10:28 UTC
Created attachment 80487 [details]
some test cases
Comment 2 Kevin Funk 2016-09-08 20:14:52 UTC
Hello!

We are working on a new clang-based C/C++ language plugin for KDevelop 5 which
supersedes the old C++ plugin in KDevelop 4. See e.g.:
https://www.kdevelop.org/news/first-beta-release-kdevelop-500-available

Due to a lack of manpower, we cannot fix bugs in the old C++ plugin. We rather
want to supply a good Clang based C++ experience for KDevelop 5 than wasting
our time on the legacy C++ support for KDevelop 4.

With the new clang-based C/C++ language plugin, the bug presented here does not
occur. In my testing. For these reasons, I'll close this bug. Please stay tuned
for KDevelop 5.

All test cases work under KDevelop 5.0.