6 Dec
2004
6 Dec
'04
11:57 a.m.
On Mon, 6 Dec 2004 azrael@demonlords.net wrote: (snip)
someone else wrote:
gcc of course leaves .o files lying around, so this is no different than C. (snip) When I use javac every file that is created is necessary for the application to run. This can't be said of the ghc compiler. Having an excuse that this is way the C compiler does it or that this is the way its always been done is to poor of a reason to even argue against. If a file isn't needed then it shouldn't be left there. (snip)
It can be useful to leave the .o files around. For instance, if you just change some source files, but not all, then you can reuse some of the old .o files instead of having to recompile everything. This gcc analogy also applies to ghc. -- Mark