I don't recall the details right now, maybe you'll find more info in the mailing list archives. I don't think the problem was simultaneous access, though. I think the problem rather was that the .NET runtime might call back into Lisp from a thread which was "foreign" to the Lisp runtime in the sense that Lisp didn't start the thread and didn't know about it.
You should probably talk to Vasilis Margioulas (don't know if he's still on the list).
I'd be happy if RDNZL worked with CLISP, but I won't be able to help you right now. I haven't used RDNZL myself for years and I didn't keep track of .NET changes. I'm not even sure if RDNZL works with the latest version of the runtime.
I hope other list subscribers can be more helpful.
Cheers, Edi.
On Thu, Aug 27, 2009 at 9:59 PM, Matthew Swankakopa.gmane.poster@gmail.com wrote:
There is a rather cryptic comment on the RDNZL home page about CLisp having GC and callback issues because of lack of thread support. Is this because the host lisp's runtime data structures need to be protected from simultaneous access by threads created by RDNZL? I ask, because clisp now has limited multi-threading support on win32, and I would like to get it to work with RDNZL.