If you use a numbered locale, you need to pass it around everywhere, which is
annoying. You can't put a reference to the locale in a global variable, since
that would defeat the purpose of being thread local.
On Thu, 9 Jun 2022, Henry Rich wrote:
What need does this address? Can it be met by having a numbered locale
to hold the task variables? What happens when a task spawns a task -
you'd want to access them all, I assume?
Henry Rich
On 6/9/2022 9:20 AM, Elijah Stone wrote:
On Thu, 9 Jun 2022, Raul Miller wrote:
"task local storage" rather than "thread local storage"
Yes. That's what I meant, but I was not clear enough.
local variables accomplish something similar
Local variables are not meaningfully mutable. IOW they are not really
_state_.
how to clean this up
Task constructors and destructors might be a good idea, and do have
prior art.
how to debug issues related to it
What do you mean?
shorter duration
If I have my way, tasks and threads will be orthogonal. If a task
migrates from one thread to another--and the former dies--it should
maintain its local state.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
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
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
