Bug 297921 - Functions definitions are not found when using fully qualified name for the declaration inside namespace curly braces
Summary: Functions definitions are not found when using fully qualified name for the d...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (old) (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-11 18:24 UTC by Lambert Clara
Modified: 2023-02-11 03:52 UTC (History)
0 users

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


Attachments
Source code corresponding to the steps showing the problem (284 bytes, text/plain)
2012-04-11 18:26 UTC, Lambert Clara
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lambert Clara 2012-04-11 18:24:35 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Build Identifier: 

When a function is declared inside a namespace, and its definition is inside namespace curly braces but has fully qualified name (i.e. redundant namespace name), kdevelop fails to link the definition to the declaration (and so we cannot jump from one to the other with ctrl+click for example).

Reproducible: Always

Steps to Reproduce:
1. Open the attached file
2. Hover func_one declaration : kdevelop finds the definition => ok
3. Hover func_two declaration : kdevelop only knows the declaration => nok
4. Remove the bar::  in the declaration of func_two
4bis. Hover func_two declaration : kdevelop now finds the definition => ok


Expected Results:  
KDevelop should have found the declaration at step 3.
Comment 1 Lambert Clara 2012-04-11 18:26:30 UTC
Created attachment 70316 [details]
Source code corresponding to the steps showing the problem
Comment 2 Andrew Crouthamel 2018-11-11 04:23:35 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:40:19 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-12 01:58:07 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-27 05:07:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-02-11 03:52:02 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!