One problem I see with 'make' clearing out class files is that it could mess up somebody who compiles from several different source trees in different projects into a single common class tree. Normally I try to keep separate source trees compiling into separate class trees but sometimes I get lazy. I'm not sure how make would keep track of class files that were there because they came from sources external to the project as opposed to class files tat corresponded to a now deleted project file.
-- Mark -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 10:25a To: [EMAIL PROTECTED] Subject: Re: [Eap-list] Clearing Cache > > Yes, sure. Just notice that it should be deleted not > immediately on deleting > the source but on the subsequent build. I must be missing something here :) In my view, I would prefer that the class file be immediately deleted on deleting/renaming the source file. Would someone care to explain the advantages of having the class file remain on disk when the corresponding source file doesn't exist anymore? Carlos -- Carlos Costa e Silva <[EMAIL PROTECTED]> _______________________________________________ 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
