Bug 185326 - Parse problem when casting to bool(*)
Summary: Parse problem when casting to bool(*)
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-23 11:56 UTC by Thomas McGuire
Modified: 2016-01-24 12:45 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas McGuire 2009-02-23 11:56:35 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

KDevelop doesn't seem to recognize that one can cast to bool(*). Without the parenthesis, this works.
This produces some problems with the .moc files that Qt 4.5 creates.

Example:

bool test(void *boolPtr)
{
    return *(reinterpret_cast<bool(*)>(boolPtr));
}

This compiles fine, but the parser reports errors (unexpected token) here.
Comment 1 Aleix Pol 2013-02-28 00:35:34 UTC
And still the case...
Comment 2 Andrey Cygankov 2016-01-23 23:00:30 UTC
I tried to reproduce the bug in KDevelop 5 and all displayed without problems. 
Probably it is necessary to close.
Comment 3 Milian Wolff 2016-01-24 12:45:06 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