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 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 comprehensive, it ought to catch almost everything else. There's a chapter in Extreme Programming Examined that discusses the Smalltalk refactoring browser. They worked up some sort of change object that can be applied, reverted, and reapplied as necessary. Any change is represented with one of these objects. Granted, that's a ways in the future. The point is, getting an 80% solution, with proper behavior to back it up, is a really really big win. Refactoring without a test suite is a risky business. -- c
