[EMAIL PROTECTED] said:
> Kontorotsui wrote:
> > Now, I don't think there is a way to recompile only the class I changed, like
> > we did in C, is this correct?
[..]
> We use make to great advantage. Our system has ~1000 java files and
> make reduces compile time dramatically. ( We use jikes, too, so that
> helps. ) Using production rules, make will only compile a java file
> when the timestamp on the .java file is later than the timestamp on the
> .class.
That doesn't take care of all the possibilities, though. If you change
the externally visible interface in a source file, other sources will
need to be recompiled as well. I haven't found a bulletproof way to
catch all the dependencies yet.
Back in the good-old C days, we carefully separated our declarations
into header files, and kept the implementation bits in .c files.
That way it was easy to figure out if you've changed an interface which
some other source depended on, and you weren't forced to recompile the
lot.
I use a messy shell script to generate make dependencies. It's too
conservative, though, and tends to recompile most everything if I change
some of the more primitive classes.
-- Pete
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
