From: Toby A. <tob...@pe...> - 2004-05-10 19:38:00
|
[I hope you don't mind me CCing this to the devel list.] The basic idea is so that you can be running under one evaluator and then create a new one and run some isolated Scheme code. The tests I added are examples of this. This could also be achieved by changing the JS.enter and JS.exit methods to save and restore the previous evaluator, but I prefer it to be explicit. The semantics of creating new threads are a bit easier to understand with an explicit stack, in my opinion. Toby. On Mon, May 10, 2004 at 01:16:12PM -0400, Ken Anderson wrote: > Why is there a stack of evaluators? > > k > > At 07:07 AM 5/10/2004 +1200, Toby Allsopp wrote: > > Okay, here are the changed files. > > > > Toby. > > > > On Fri, May 07, 2004 at 08:12:43AM -0400, Timothy John Hickey wrote: > > > Hi Toby, > > > Could you send me a tar ball of the changed files? > > > I'll have a look and test it out on some of my larger applications.... > > > Thanks, > > > ---Tim--- > > > > > > > > > On May 6, 2004, at 9:15 PM, Toby Allsopp wrote: > > > > > > > After some delay, here is the promised patch that allows one JVM > > > > to host multiple JScheme instances that are isolated (or not if > > > > you want) from each other. I can provide the entire changed > > > > files on request. > > > > > > > > Note that there are two new files: src/jsint/Evaluator.java and > > > > src/jscheme/SchemeEvaluator.java and one removed file: > > > > src/jsint/SI.java. |