Bug 206554 - c++ support, function overloading, automatic definition update
Summary: c++ support, function overloading, automatic definition update
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-06 22:07 UTC by Jörg Pfähler
Modified: 2016-01-26 18:05 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 Jörg Pfähler 2009-09-06 22:07:54 UTC
Version:           0.9.95 (svn from 06.09.2009) (using KDE 4.3.1)
Compiler:          g++ 4.4.1 
OS:                Linux
Installed from:    Ubuntu Packages

Consider the following piece of code

struct test
{
  void f();
  void f(int i);
};

void test::f()
{
}

when you add the "int i" in the function definition you get an "update Definition" dialog, which is superfluous in this case and which alters the declaration of void f() (which is wrong, because it won't compile afterwards). See http://img186.imageshack.us/img186/1739/kdevelop4.png
Comment 1 Milian Wolff 2010-06-16 00:19:34 UTC
confirmed
Comment 2 Lukas Jirkovsky 2010-12-31 12:51:45 UTC
Looks very similar to the bug #211652
Comment 3 Andrey Cygankov 2016-01-23 22:21:03 UTC
I tried to reproduce the bug, and now the dialog is not displayed when completely written "int i" and does not change when you click on the dialog when the "int i" still is incomplete. Probably it is necessary to close.
Comment 4 Milian Wolff 2016-01-24 12:46:32 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
Comment 5 Jörg Pfähler 2016-01-26 18:05:50 UTC
> Sorry for the inconvenience, I hope you understand the reasoning above.
Of course! I am actually quite happy that you switch to clang in favor of rolling your own parser.