Menu
▾
▴
#17 class for function calls that are not thread safe
I am missing a synchronization primitive that can ease the
transition from single to multithreaded programming. I am
thinking about a class that combines a thread with a Guard object.
Can it be added without help from the Pthread API? Did you hear
about such an idea before?
Would you like to join the
discussion "class for function calls that are not thread safe"
(http://groups.google.de/groups?group=comp.programming.threads&selm=40ed1d8f.0309240440.34faf8c2%40posting.google.com)?
Logged In: YES
user_id=572001
Would you like to support that work or command objects can be sent to a target thread like that can be done with TCL scripts by the function "thread::send"?
http://cvs.sourceforge.net/viewcvs.py/\*checkout*/tcl/thread/doc/html/thread.html?rev=1.10
Logged In: YES
user_id=217
We often wrap such functions in a mutex, since the mutex
will singularize calls into the object. We probably do not
do this for enough of the functions which may be unsafe,
however. Are you suggesting an explicit "sync..." generic
function wrapper, ala what Java does?
Logged In: YES
user_id=572001
Can you see from the source
code "http://groups.google.de/groups?
selm=40ed1d8f.0311150646.4641684a%
40posting.google.com" what I want?