The issues you mention of how many threads to use and how to use them
efficiently when there are many tasks have generated considerable debate
among the implementers.
I think you're saying that you plan on providing library support, so
that the useful operations will not have to be re-implemented, and
that typical case use, outside of classroom presentation, will not use
this primitive. But if that's the case... I'm not sure why threading
wasn't built using foreigns.
I expect someone will provide library support. I don't think much is
needed.
I used t./T. rather than foreigns so that it would be easy to find the
primitives in NuVoc, and easier to remember what the names were. And,
these primitives aren't really 'foreign' in the way file read/write are.
Henry Rich
--
This email has been checked for viruses by AVG.
https://www.avg.com
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
