"John Keiser" <[EMAIL PROTECTED]> writes:
> The chicken-and-egg problem is only relevant for distributions that have to
> build Java code at the client, which it shouldn't have to do if the classes
> are not machine-specific.
I see your point and raise you another question. From a purist point
of view does it matter? Would RMS (purist of the pure) happily use
.class files compiled using a possibly proprietary means? Anyway, you
can set the JAVAC environment variable before compiling to control
which compiler is used already. I agree with you that we can
basically ignore the java compilation problem if we want to from the
end user's perspective.
Just found a neat program written in Java, JavaDeps. You can read
more at http://www.cs.mcgill.ca/~stever/software/JavaDeps-2/
This is for accurately tracking dependencies between Java source files
and recompiling them as needed.
Brian
--
|-------------------------------|Software Engineer
|Brian Jones |[EMAIL PROTECTED]
|[EMAIL PROTECTED] |http://www.nortel.net
|http://www.classpath.org/ |------------------------------
