At 10:36 26/3/01 +1000, Conor MacNeill wrote: > >----- Original Message ----- >From: "Stefan Bodewig" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Monday, March 26, 2001 5:58 PM >Subject: [DISC] class loading > > >> * force resolution of classes on loading to identify classloader >> issues early. (At least in global classloader). > >-1, what benefit does knowing this early give you? You may end up loading a >whole lot of classes into the VM you never actually need with consequent >memory issues.
For any semilarge system that is going to be carrying as many classloaders around as I suspect Ant2.0 will - it becomes an absolute PITA to try and figure out where/when/why a ClassNotFound exception arises from. It can be gotten around by smart coding but I don't see the need for the extra complexity. Remember that the classes are almost always loaded right before you instantiate a task so force loading it is not going to have any adverse effects as virtually all the classes will be loaded anyway. Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
