RE: VAJava???

Joe --

Eclipse has all of this plus a whole lot more.  Support for various
refactorings is especially strong.  Moving a method from one class to
another consists of cut/paste.  Or, there are special refactoring
options for things like "Pull Up" which automatically moves a method or
field to a superclass of the containing class.

It doesn't use WTE, which is a kludge.  Instead, WSAD uses the real WAS.

For getters and setters, you can specify prefixes and suffixes to
remove.  For example, I like to name my fields m_foo but I want the
methods to use getFoo and setFoo, not getM_foo and setM_foo.  Eclipse
handles this as well.

Gary

> -----Original Message-----
> From: java400-l-admin@midrange.com
> [mailto:java400-l-admin@midrange.com] On Behalf Of Joe Pluta
> Sent: Thursday, September 19, 2002 9:04 AM
> To: java400-l@midrange.com
> Subject: RE: VAJava???
>
>
> > From: Bruce Jin
> >
> >
> > 3. The ability to easily move a method from one class to another.
> >
> > ?
>
> I use this when I promote a method from a subclass to a
> superclass, Bruce, or vice versa.  It's also nice to be able
> to copy a method from one class to another.
>
> I also forgot a couple of features I use all the time:
>
> 1. When creating a subclass of an abstract class, generate
> the stubs for all the required methods.
>
> 2. After adding a bunch of instance variables, automatically
> generate the setters and getters for them (this is great for
> programming beams!).
>
> Joe
>
> _______________________________________________
> This is the Java Programming on and around the iSeries /
> AS400 (JAVA400-L) mailing list To post a message email:
> JAVA400-L@midrange.com To subscribe, unsubscribe, or change
> list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
> or email: JAVA400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
>