Overview
| Artifact ID: | 28f37891118c0086170348f7bb656c080848b1a1f1b8c4186773be89571684fe |
|---|---|
| Ticket: | b5709ea9060d17f58ba48110351c964b3408e362
[::thread::send -async] posting order not respected when sending to current thread |
| User & Date: | sebres 2018-07-31 16:55:21 |
Changes
- icomment:
Now I understand your objection (I was just confused with both after(timer) events from your example and your description). Indeed it is possible..., but not what you provided as block "to remove", this one would be enough to remove: [https://core.tcl-lang.org/thread/artifact?name=61003585d6458178&ln=2752-2756|61003585d6458178(lines 2752-2756)] Of course with move of `Tcl_MutexUnlock(&threadMutex);` (line 2747) 2 lines down, into block `if ((flags & THREAD_SEND_WAIT))`. I'll take a look later as regards the test-cases and some other dependencies and behavior etc.
- login: "sebres"
- mimetype: "text/x-fossil-wiki"