Tcl package Thread source code

Ticket Change Details
Login
Overview

Artifact ID: 5bf140d6bdc1477af26e76ff56086177f4ffabf6b1e431e278dca26c4afcf2a7
Ticket: 90de9ddf94ecfb6bacd5e754919a21d31fe3f25a
Checking data consistency for unlocking of mutexes
User & Date: elfring 2019-05-10 16:56:08
Changes

  1. closedate changed to: "2458614.20565142"
  2. closer changed to: "elfring"
  3. icomment:
    > so if main thread switch it within lock,
    
    Now I imagine that this undesired action can be prevented by referring to the mentioned context information by a local TCL variable instead of using the command “[tsv::get shared context]” in the worker threads.
    This can be achieved by a concatenation of two code parts like the following.
    
       thread::create [string cat "set context $x\n" $suffix]
    
    
    > … your worker pool (context) is protected by "working" counter, which is not guarantee at the moment that all workers really counted …
    
    I have changed the software design to an approach which works with termination notifications from TCL worker threads.
    Unfortunately, it contains also open issues for further development considerations.
    
  4. login: "elfring"
  5. mimetype: "text/plain"