"Jonas Kvarnstr�m" wrote : > Alain Ravet wrote: > >If an unused method calls another unused method, the 2nd one is no longer > >considered usused. > >I think it should > > > I'm not sure I agree with you.
I'm not sure either, but I feel there is something to do here. Not sure how. A wizard maybe :-))) ? Alain > The way it works right now, if I see that a method is unused and I know > I don't intend to add a new call to that method anywhere, I can safely > remove it. Then the file is re-parsed and maybe a few more methods are > shown as unused, and I can go on removing code. > > If this is changed, then I might remove an "unused" method unused2() and > end up creating a syntactic error in unused1(), so I also have to remove > unused1() creating a syntactic error in unused0(), but I know that > unused0() will be used in the future so I have to go back and undo > removing the methods. > > Maybe the "unused although chained" detection should only be part of the > global "find unreachable code" function which is planned for Ariadna? > Especially if adding this to the basic syntactic highlighting procedure > would take more time and slow down the editor (which I don't know if it > would). > > This isn't a strong opinion, just a few thoughts... _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
