Bug 311964

Summary: Q_REQUIRED_RESULT not parsed properly
Product: [Applications] kdevelop Reporter: Aleix Pol <aleixpol>
Component: Language Support: CPP (old)Assignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: normal CC: craftplace.ms
Priority: NOR    
Version First Reported In: git master   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Aleix Pol 2012-12-20 04:27:47 UTC 
The Q_REQUIRED_RESULT macro isn't parsed properly.
It expands to: __attribute__ ((warn_unused_result))


Reproducible: Always

Steps to Reproduce:
1. Go to qstring.h
Actual Results:  
http://wstaw.org/m/2012/12/20/plasma-desktopZ12541.png
Comment 1 Aleix Pol 2012-12-20 04:28:22 UTC 
Just to make sure, if I remove the macro, then it works fine.
Comment 2 Aleix Pol 2013-03-31 00:48:34 UTC 
Moving all the bugs from the CPP Parser. It was not well defined the difference between it and C++ Language Support and people kept reporting in both places indistinctively
Comment 3 Kevin Funk 2013-05-22 11:06:31 UTC 
Worksforme.
Comment 4 Kevin Funk 2013-05-22 11:21:17 UTC 
Hm, nope -- it doesn't. I have one session open where it works, but it another one it doesn't.
Comment 5 Andrey Cygankov 2016-01-23 20:17:07 UTC 
I tried to reproduce the bug(with different sessions also) - it no longer valid.
Comment 6 Milian Wolff 2016-01-23 21:16:09 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.

If you think this bug is applicable to Clang/KDevelop 5, please reopen the
report and add new information on how to reproduce the bug there.

Sorry for the inconvenience, I hope you understand the reasoning above.

Cheers