Bug 323414 - nested macro argument not matched
Summary: nested macro argument not matched
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: 4.5.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-12 12:51 UTC by James Hogan
Modified: 2018-03-25 22:24 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Hogan 2013-08-12 12:51:30 UTC
The following code has a nested macro which is used. Moving over mymacro1 does show correct expansion in this case, but the tmp argument doesn't highlight to match it with the other tmp's. It does for the non-nested macro (mymacro2) or when the function/macro is undeclared (something_else).

#define mymacro2(val2) val2
#define mymacro1(val1) mymacro2(val1)

int a()
{
	int tmp;
	mymacro1(tmp);
	mymacro2(tmp);
	something_else(tmp);
}
Comment 1 Kevin Funk 2018-03-25 22:24:36 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.