Re: [Jscheme-user] Re: Multiple independent interpreters

[Toby A. <tob...@pe...>]

On Fri, Mar 12, 2004 at 02:11:17PM -0500, Jonathan A Rees wrote:
> 
> Each interpreter instance potentially also needs its own class loader
> (for use by scheme code, not by jscheme itself).  Don't forget to
> provide a way to set it in a newly created instance.

Yes, I was just looking at the class loader stuff in jsint.Import, and
that will need attention for any serious J2EE use, and probably any
serious use embedded in a larger application.

The current behaviour is to set the current thread's context class
loader to the class loader that loaded jsint.Import when jsint.Import is
initialised, then always use the class loader that loaded jsint.Import.

I propose that better behaviour is to never change the context class
loader and to use either a user-specified class loader or, if none has
been specified, the current thread's context class loader.

> I'm really glad that multiple interpreter instances is being
> discussed.  The demand for this is an inevitable consequence of the
> project's success.  Soon you may find two applications that both use
> jscheme, that need to interoperate in the same Java VM, and neither
> even *knows* that the other is using jscheme, and this is as it should
> be.

I absolutely agree.

Toby.