It's there now, but the code is pretty "alpha" in my opinion. I think it should stabilize in the next few weeks.
"Sebastian Hauer" <[EMAIL PROTECTED]> writes: > Not exactly refactoring but unbelievably useful. > Find the usage of a variable or method name. > > If JDEE or some other free emacs mode is able to provide this feature > please let me know. > > Regards, > > Sebastian > > -----Original Message----- > From: Nascif Abousalh-Neto [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 02, 2002 6:23 PM > To: [EMAIL PROTECTED] > Subject: Refactoring Wish List > > > > So far we have: > > 1. Changing class name (and all references). > 2. Changing names of any choosen class member - field, method (and all > references) > 3. Changing package for one or more classes with 'one click' (and all > references) > 4. Moving class to different package > 5. Create factory method in place of constructor > 6. Extract method from selected piece of code > 7. Extract super class or interface for selected piece of code and set > of fields > 8. Deleting classes/methods/attributes > 9. Copying classes into other packages > 10.Copying methods/attributes into other classes > > I would like to see some features from Transmogrify, which may not be > necessarily refactorings but are easy to implement once you have a > refactoring framework (which requires the complete syntax trees plus > reference resolution) in place: > > 11. Wrapping a block of code in a try/catch (exceptions needed extracted > from the signatures of the methods in the block) > > 12. Finding out unsused variables/methods/classes > 13. Finding out shadowed variables/methods > > Maybe we should have a page somewhere and vote? A system like bugzilla > to track requirements/bugs and get user input on the most desirable ones > would be nice. > > For a comprehensive list of Refactorings as documented by Martin Fowler, > check http://www.refactoring.com/catalog/index.html > <http://www.refactoring.com/catalog/index.html> > > Regards, > Nascif
