This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Re: Thread-safe eval()
If is really an internal problem you might try the following
work-arounds:
o if the only way this code gets called is through your java code that
calls eval, maybe you can put a java synch block around your code that
calls eval in java
o dont call eval -- write the code in a .scm file that defines a java
class using define-simple-class and then instantiate that class and
call the code from java. This might work if the problem is in "eval"
and will also be faster code.
-will
William Shulman writes:
>
> ahh, you are probably right. I did not consider that (maybe I should
> have read more carefully). Sorry Jost.
>
> -will
>
> Per Bothner writes:
> > William Shulman wrote:
> >
> > > you can try using the 'synchronized' form:
> >
> > My reading of the question was that the synchronization
> > problem appears to be at the Kawa internals level.
> > Something that is shared but shouldn't be, or something
> > that isn't synchronized in the Kawa internals. Using a
> > Kawa (synmchronzied ...) form wouldn't help then.
> >
> > I do have a unfinished rewrite of the environment/symbol code
> > to make it work better for multiple independent interpreters,
> > but I don't know if that would help Jost's problem.
> > --
> > --Per Bothner
> > per@bothner.com http://per.bothner.com/