Bug 333128 - Auto-completen fails to show members through dereferencing operator
Summary: Auto-completen fails to show members through dereferencing operator
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: All editors (other bugs)
Version First Reported In: 4.6.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-06 15:32 UTC by roland
Modified: 2023-02-07 03:55 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 roland 2014-04-06 15:32:32 UTC
Using the following situation:

SomeFunction( *foo.bar() );

If you type up to "*foo." and you try to get an auto-completion KDevelop displays nothing at all since it fails to ignore the dereferencing.

Reproducible: Always

Steps to Reproduce:
1. Type "*foo." where something is a pointer to a class containing members
2. Use auto-complete (or automatic auto-complete)
Actual Results:  
Auto-completion complete breaks down showing nothing except the standard Kate auto-completion menu for words found in the document

Expected Results:  
List of membry of "foo".

The C++ standard defines the operator ordering in a way that member selection (. or ->) is tighter bound than dereferencing/refererencing operators(* or &). This means the auto-completer should know that if *foo. is written the dereferencing belongs to whatever comes AFTER the period and thus that it should show members of foo as if the dereferencing operator does not exist.
Comment 1 Andrew Crouthamel 2018-11-11 04:24:17 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 2 Andrew Crouthamel 2018-11-21 04:33:02 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 3 Justin Zobel 2023-01-08 22:44:56 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 4 Bug Janitor Service 2023-01-23 05:05:03 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 5 Bug Janitor Service 2023-02-07 03:55:28 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!