Bug 72726 - [Refactoring] Will not allow refactoring of overloaded operator methods
Summary: [Refactoring] Will not allow refactoring of overloaded operator methods
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-refactoring (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-26 15:34 EDT by Sean Evoy CLA
Modified: 2020-09-04 15:26 EDT (History)
6 users (show)

See Also:

Attachments
Minimal project to verify the enhancement is still needed (1.91 KB, application/x-zip-compressed)
2013-04-22 19:28 EDT, Jesse Weinstein CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Evoy CLA 2004-08-26 15:34:40 EDT 
Test case: RNM35
CDT I200408260400
Eclipse M200408250800

First, you have to select the operator method in the outline view or 
navigator; it is not possible to do so from the source code (I guess the 
selection cannot distinguish that operatorXX is a single token). Next, when 
you try to rename the method (i.e. operator+= -> operator*=) the dialog 
complains that the name is invalid.
Comment 1 Doug Schaefer CLA 2007-08-21 10:57:03 EDT 
Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'.
Comment 2 Jesse Weinstein CLA 2013-04-22 19:28:14 EDT 
Created attachment 229999 [details]
Minimal project to verify the enhancement is still needed

Verified with eclipse-SDK-4.3M5a-win32-x86_64. However, this is an enhancement, not a bug. Currently, you *can* select the operator from an editor, and it will let you appear to change it, then bring up the helpful error message when you press Enter. When selecting it from the outline, it immediately gives you the error message.

As this is an enhancement, it should be marked as such for purposes of priority.