Yes - mostly (but not entirely) as something to be avoided. You can emulate threading with gerunds, if you are also willing to maintain a stack. J's implementation also has contained some overhead from threaded attempts which wound up causing more problems than they solved. But mostly threaded code winds up being a lot of wasted motion, in the context of the kind of program which J is well suited for.
Threaded code can be nice, however, for fast animated contexts, such as games. J is suitable for tools to edit data structures used in games, and it's suitable for exploring concepts useful in games, but I think you'll need to refactor a threaded game architecture before using J to implement it. That said, threading can also be nice for servicing user interface mechanisms. If jqt had a way of interrupting a J program, the interrupt servicing code would need to be an independent thread. Thanks, -- Raul * On Mon, Jan 25, 2016 at 8:54 PM, 'Pascal Jasmin' via Programming < [email protected]> wrote: > https://en.wikipedia.org/wiki/Threaded_code > > Does this concept apply to J's implementation in any way? > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
