In general, it is not a good idea to assume any class/method is thread safe,
even in Java. Unfortunately, Java tends to give programmer a false sense of
security when it comes to threading issues. In Java, it is too easy to
create threads, IO packages must use threads, and synchronization
-Original Message-
From: Mike Schwartz [mailto:[EMAIL PROTECTED]]
I thought it was the JNI / C code side that wasn't thread
safe. You're
saying it's the Interp pure Java code that's the problem? In
that case
you could define an abstract class with all the Interp interfaces
