Bug 139233 - When auto-creating methods like 'setXxx(xx)' and 'getXxx()', provide standard implementation
Summary: When auto-creating methods like 'setXxx(xx)' and 'getXxx()', provide standard...
Status: VERIFIED DUPLICATE of bug 41542
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-28 12:41 EDT by Alex Blewitt CLA
Modified: 2006-04-30 16:57 EDT (History)
0 users

See Also:

Attachments
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 Alex Blewitt CLA 2006-04-28 12:41:48 EDT 
If I'm creating well-known methods like setters, getters (or issers?), it might be possible to automatically suggest a default implementation. Of course, this would be done by choosing a separate proposal (e.g. 'create setSomething()' and 'create setSomething() (with default implementation)'.

Set methods could take their argument(s) and assign them to private fields of a similar name (or offer to create them if they don't already exist). Get/is methods could do the same.

It would make test-driven development a bit faster :-) Of course, this is something to be resolved later for the 3.3 run, but hopefully it will get reopened in 3.3 ...
Comment 1 Martin Aeschlimann CLA 2006-04-29 19:17:03 EDT 

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