And in addition to the reasons written by Ash. It will be just consistent with the fact that the class files are not updated automatically as you type code. The same should then hold for other operations like deletion. Some other IDEs (VAJ or Eclipse) do it in another way (they automatically update class files on save and some other events). We don't. But both policies should be consistent and not mixed!
Best regards, Valentin Kipiatkov ----------------------------------------------------------- IntelliJ Software, http://www.intellij.com/ "Develop with pleasure" ----------------------------------------------------------- ----- Original Message ----- From: "Ash Searle" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 10, 2002 9:13 PM Subject: RE: [Eap-list] Clearing Cache > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > > Behalf Of Carlos Costa e Silva > > Sent: Wed 09 January 2002 18:25 > > To: [EMAIL PROTECTED] > > Subject: Re: [Eap-list] Clearing Cache > > > > Would someone care to explain the advantages of having the class file > > remain on disk when the corresponding source file doesn't exist > > anymore? > > You'll want to keep the class files if you're still running the > program you're developing. I often keep a copy running and make > changes - I could come up with many contrived examples for why. > Before people start saying the .class will already be in the JVM, > consider programs that use: > > Class.forName(...); > > ResourceBundle.getBundle(...); > > > Presumably, by the time you're ready to try making the program again, > you're ready to close down the last copy you had running, so it's > then the sensible time to delete the .class files. > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
