> -----Original Message-----
> From: neal@... [mailto:neal@...]On Behalf Of Neal M Gafter
> In short, I don't think it's necessary to load the compiler into its own
> class loader in most circumstances, but you're welcome to try it either
> way you please. If you try it both ways and can share some data on the
> relative performance (space and time) I'd love to hear from you.
I am considering what will be involved in loading javac into its own
classloader. For this to be effective, I believe tools.jar cannot be on the
system classpath as the classloader will just delegate to the system loader.
We can play some tricks around that, I guess, but they are a little risky.
What I would like to know is whether there is any standard for where the
compiler classes are located. Are they always in tools.jar. Also is there
some standard for where to find tools.jar. I had the impression that on some
OSs (Mac OSX?), the compiler classes are in the boot classpath. Not sure