Just a thought - I reckon it should be relatively straightforward to spot "feature envy", one of the "bad smells in code" mentioned in Fowler's Refactoring book. Count the number of references to other classes within a method (especially where casts are involved, I suppose), and if this is high, suggest moving the method.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just a thought - I reckon it should be relatively straightforward to spot "feature envy", one of the "bad smells in code" mentioned in Fowler's Refactoring book. Count the number of references to other classes within a method (especially where casts are involved, I suppose), and if this is high, suggest moving the method.
This seems related to this one:
http://sourceforge.net/tracker/index.php?func=detail&aid=585557&group_id=56262&atid=479924
but it's not exactly the same thing. Danny, could you put in a feature request thingy for this one?
Thanks,
Tom
News?