One possible approach to this issue is to have a plugin interface which allows users to define new classloaders the same way new functions are added. This is particularly useful in the case of IDE, where a user starts up Eclipse and it loads the state of the last project.
In a dynamic environm
I think Alan Moore wrote:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Would it be possible to have the (import) function fail or give a warning
> when the specified package and/or class doesn't exist. Currently,
>
> (import com.package.doesnt.exist.MyMispeledClass)
>
> doesn't give
Would it be possible to have the (import) function fail or give a warning
when the specified package and/or class doesn't exist. Currently,
(import com.package.doesnt.exist.MyMispeledClass)
doesn't give any indication that something is wrong.
alan
Alan Moore - mailto:[EMAIL PROTECTED]
Ciphergen
