Re: refactoring using parser

In article <[email protected]>,
    Kaleb Pederson <[email protected]>  writes:

> * Refactoring.  At absolute minimum, I'd need the following:
>   * Rename (which may require renaming files)
>   * Move
>   * Extract Method
>   * Inline Method
>   * Pull up
>   * Extract Interface
> * View type hierarchy of currently selected instance / object
> * Continuous Test Runner (run unit tests in background on file save
> and display results)
> * Re-run only failed tests or certain test packages
> * Debug test, stopping at breakpoints, etc.
> * Instantaneous feedback on bad syntax and semantics
> * Find all references of * (an instance variable, a type, an interface, etc.)
> 
> ... and I could go on despite being a huge Vim fan.  I save a huge
> amount of time using automated refactoring tools.

That's an interesting list of refactorings.  I do Rename, Extract
Method and Extract Interface a lot.  I haven't done so much Inline
Method or Pull Up.  By "Move" I assume you mean "move this method from
this class to another class"?  What automated refactoring tools
support this?  Even ReSharper only supports moving whole types or
static members and doesn't support moving methods.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
 <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>

      Legalize Adulthood! <http://legalizeadulthood.wordpress.com>


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/