Maybe if enough of us indicate that this is really important, J Engine would end up being thread-safe (or re-entrant or however you are used to call it). From what I gather there isn't that much that needs to be changed for J Engine to become fully thread-safe. It seems like it's almost there. I am beginning to familiarize myself more and more with JE engine source. But I am not yet ready to fix the thread-safety related issues. But maybe others are familiar enough to be able to do it, if this is seen as an important need.
I believe in this day and age is important for J Engine to be thread-safe. Do other people think so too? Even more, further down the road J language should have thread handling support included, to keep up with the times, I think. On Fri, Apr 26, 2013 at 6:22 PM, Scott Locklin <[email protected]>wrote: > I'm wondering if anyone has yet had a go at integrating ZeroMQ with J. I'd > like to code up the pub/sub pattern for a ticker plant. > I was just going to use the 15!:0 FFI and do calls on ZeroMQ pointers. The > only thing which gives me pause is ZeroMQ has an underlying threading model > which might do weird things; I have had bad luck working with raw pointers > with underlying threads called from J in the past. > > 0MQ's threading model: > http://www.zeromq.org/whitepapers:architecture > > -Scott > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
