Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354493

Summary: Add feature for listing update references
Product: [Tools] CDT Reporter: Øystein Kolsrud <kolsrud>
Component: cdt-source-navAssignee: Project Inbox <cdt-source-nav-inbox>
Status: CLOSED DUPLICATE QA Contact: Markus Schorn <mschorn.eclipse>
Severity: enhancement    
Priority: P3 CC: aleherb+eclipse, cdtdoug, yevshif, zeratul976
Version: 8.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Øystein Kolsrud CLA 2011-08-11 09:27:39 EDT
Build Identifier: 20110615-0604

I often have cases where I would like to list all places where a certain object is modified. I would therefore like to have a feature very similar to the "References" actions in the right button menu of the C++ editor called something like "Write References" that only list the references where the object is updated. Example:

If I want to list "Write References" for an object named "x" then I would like line 1 and 2 of the following list to be listed, but not line 3:

1) x = 0;
2) y = x++;
3) y = x;

This is almost identical to what is already done with color highlighting in the source browser, so it seems that the functionality is already there. It's just that I want to be able to search my entire project and list the write references in the search list so that I can use that list to navigate between all places where updates occur.

Reproducible: Always
Comment 1 Markus Schorn CLA 2011-08-16 09:36:37 EDT
You can look at the usage of a global variable via the call-hierarchy. It annotates the r/w references.
Comment 2 Anton Leherbauer CLA 2011-09-02 05:28:16 EDT
And if the Call Hierarchy also had a filter for read/write access it would be perfect.
Comment 3 Nathan Ridge CLA 2014-08-25 18:39:11 EDT
An option to filter references to writes only was added in bug 437067.

Is there anything left to be done for this bug?
Comment 4 Nathan Ridge CLA 2016-12-29 01:12:18 EST

*** This bug has been marked as a duplicate of bug 437067 ***