Bug 206398 - parser, using declaration and function definition outside of class definition
Summary: parser, using declaration and function definition outside of class definition
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-05 17:13 UTC by Jörg Pfähler
Modified: 2016-01-24 12:44 UTC (History)
1 user (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 Jörg Pfähler 2009-09-05 17:13:15 UTC
Version:           0.9.95 (svn from 05.09.2009) (using KDE 4.3.0)
Compiler:          g++ 4.4.1 
OS:                Linux
Installed from:    Ubuntu Packages

The parser does not recognize the foo in "void bar::f(foo& x){ ... }"

namespace test
{
  struct foo{};

  struct bar
  {
    void f(foo& x);
  };
}

using test::bar;

void bar::f(foo& x)
{
}

see http://img245.imageshack.us/img245/6621/kdevelop1.png
Comment 1 Andrey Cygankov 2016-01-23 22:39:41 UTC
I tried to reproduce the bug in KDevelop 5 and everything displayed without error.
http://i.imgur.com/WqNTtrA.png
Probably it is necessary to close.
Comment 2 Milian Wolff 2016-01-24 12:44:37 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