Overview
| Artifact ID: | f8d041e8c74540018ba2a421ae174f2974fedf52e3bf7b9a31fe79250b83e092 |
|---|---|
| Ticket: | c6057948e5f884435ee35517008db0205f286a5e
tsv commands break thread access rules for Tcl values |
| User & Date: | dgp 2018-04-03 12:38:03 |
Changes
- assignee changed to: "aku"
- icomment:
The history of the objThreadMap restriction starts with these checkins by Mo Dejong. First he tried adding a field to the Tcl_Obj struct: https://core.tcl.tk/tcl/info/50c5d9ac11c96d30 And then followed up with the objThreadMap approach: https://core.tcl.tk/tcl/info/4dc4a16832209a53 The checkin and ChangeLog comments indicate the worry was about races between multiple threads manipulating the refCount field. This is a valid concern, but with mutex care and sufficient thread isolation it can be managed without imposing such a strong constraint.
- login: "dgp"
- mimetype: "text/plain"