Any "dead-code" detection in Java source will be made more difficult by the use of the Reflection API. Just wanted to mention it because we use Reflection quite a bit to invoke some internal code, in order to fail gracefully if a dependent library or JRE version is not present.
Jason Boehle [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 4:39 AM To: [EMAIL PROTECTED] Subject: [Eap-features] dead-code deleting Hi Dimitry, I agree in principal with your statements but I think that in practice people have to reactions to dead-code in a large development teams with a lot of legacy code: -Even though you developers are convinced some piece of code is no longer used they don't want to blamed if it turns out that for some reason the dead-code was not really dead. -They can go with a sense of purpose and arbitrarily delete code. commenting rather then deleting adds ease of use. -I always compile and run any code after doing this kind of cleanup. It's nice to know you can easily undo the damage or confirm by deleting. -you can leave it in for others to review and confirm deleting before actually deleting -Since more often than not the code is the documentation it is good for developers to see at least intermittently that maybe some algorithms/objects are no longer or temporarily not being used. Yes Code can be resurrected from source control... but that often lacks just as much information as commented code does 1 month after it has been commented out. I just think that commenting out code is more social. Further I sometimes want to leave commented code in my work as reminders of what I have yet to implement. Anyway... I am getting far away from the purpose of this forum.... but just to re-iterate I believe that any dead-code detection should not only offer the possibility to delete it. Florian Hehlen UBS Warburg Europastrasse 1 8152 Opfikon, ZH SWITZERLAND phone: 01 239 5162 -----Original Message----- From: yole Sent: Donnerstag, 1. November 2001 07:59 To: eap-features Cc: yole Subject: Re: [Eap-features] RE: Automatically create compiler output path) Hello Florian, Wednesday, October 31, 2001, 5:03:18 PM, you wrote: FHuc> on the subject of dead-code tracking... FHuc> it would be nice if one could after finding dead code choose on a FHuc> method/member basis to delete OR COMMENT OUT. This is an important FHuc> feature if you are doing team development and do not want to appear to FHuc> be deleting others work... take for example the case where a developer FHuc> had to stop working on implementation mid-way. They might leave FHuc> seemingly dead or not yet live code! If you know that someone is working on the code and stopped mid-way, then why touch this code at all? Surely, commenting it may annoy that developer a little less, but annoy it will, in any case. :-) And if this code is indeed dead (and not just unfinished), then it should be deleted altogether. Old code should be preserved in source control systems, and not in comments. After a month, you will never know why the code was commented and whether it would be safe to delete it. -- Best regards, Dmitry mailto:[EMAIL PROTECTED] _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
