Well, that is sort of how we handle it. We don't base our decisions for
the compiler and debugger on the presence of tools.jar in the preferences,
but rather on whether the classes load successfully, either through
classloading methods or direct instantiation. We're always careful either
way about ClassNotFoundExceptions and NoClassDefFoundErrors, in any event.
Was there something specific in DrJava's code you were referring to?
Charlie
Peter Centgraf wrote:
> This was just posted to the java-seed list at Apple:
>
>> Programs should not assume that certain classes are always and only
>> available when certain JARs or filenames are present. Instead, programs
>> should probe for the necessary class using Class.forName()
>
>
> He's got a good point here. This might be a better way of checking for
> debuggers, compilers, junit, and other such optional DrJava add-ons.
>
> --
> Peter
>
|
