Oleg Kobchenko wrote: > I always assumed that you can run several J instances > on different threads simultaneously. One big example is > ASP and ASP.NET: I tested it and it worked. Another example > is my jasync (async.ijs), which with a help of > external callback, encapslating J instance on its stack, > is also able to do it.
As long as only one J thread is running at a time, in a process, there isn't much room for anything to go wrong. (Maybe some memory loss, if you've called jinit more than once.) Even multiple threads running at the same time might work, as long as they don't step on each other. By "step on each other", I mean: try to update the same data structures at the same time (symbol table, memory pool, mapped files, maybe some primitives which use static or global storage). Even there, damage might be limited. That said, in multi threaded applications, there's a huge gap between "it works" and "it always works reliably". -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
