I use boost::thread which is cross-platform and it has a few variations of fast or recursive mutexes and locks. I also quite like the philosophy of "scoped locks" so you do not forget to unlock the mutex (the destructor does that for you) - similar philosophy could be ie applied to pushing/poping drawing transformation matrices or other programming tasks where you need to unroll/pop/release something as many times as you call it in the first place.
I have love/hate relation with boost: some parts I like a lot, some seem to be quite bizzare - the thread library is a nice part. R. dimatura wrote: >> If you need to do some really *looong* processing, don't do it from a >> callback, find some other way to manage it (I usually spin of a worker >> thread) to ensure that the GUI stays alive. >> > > Thanks for the answer. By the way, what do you use for threads? It seems FLTK > doesn't have most of the things you'd usually use with threads, like locks, > monitors, etc. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
