On Mon, Sep 17, 2001 at 12:29:56AM -0600, chromatic wrote:
Ideally, there'd also be a comprehensive test suite to run after the
refactoring to see what breaks. If the browser doesn't catch
everything, and if the test suite is kept at 100% pass, and if the
coverage is close enough to
In article [EMAIL PROTECTED], Andrew M. Langmead
[EMAIL PROTECTED] wrote:
So I'd think the best thing to do to make something that can produce answers
to things like what are the implementors of foo.
Ideally, there'd also be a comprehensive test suite to run after the
refactoring to see what
On Sun, Sep 16, 2001 at 11:04:48AM -0400, Andrew M. Langmead wrote:
So I'd think the best thing to do to make something that can produce
answers to things like what are the implementors of foo.
Yes, the two most important things are:
Who are the implementors of methods/functions called
On Sat, Sep 15, 2001 at 10:45:50AM +0200, Michael G Schwern wrote:
That's it. And the refactoring browser just helps you with the
mechanics of that.
THAT'S SO EASY! If it works for them, it can work for us.
So, I can handle the underlying mechanics no problem. Who's good at
GUIs?
I'm at, of all places, the Scandinavian conference on Java And
Object-Orientation (JAOO). Somebody stumbled upon the How To Be Lazy
tutorial and thought I knew something about design methodologies.
If nothing else it has the unique advantage of not being in New York.
So who do I meet here but
On Sat, Sep 15, 2001 at 10:45:50AM +0200, Michael G Schwern wrote:
1) Change this() to that() in both 'Foo' and 'Bar', and change all
instances of $obj-this to $obj-that.
2) Walk through each call to $obj-this and decide if it should
be changed to $obj-that.