Any insights here? I'd be happy to add some documentation to Mutex if someone can verify what the intended behavior is... -atw "sending emails to webkit-dev during WWDC is probably futile, I know :)"
On Sat, Jun 6, 2009 at 8:57 AM, Drew Wilson <atwil...@google.com> wrote: > I can't seem to find any documentation as to what the expected behavior of > Mutex.lock() is with regard to calling lock() recursively on the same > thread. > Looking at the pthreads implementation, it appears that when we create the > mutex we pass null as the attributes, which gives us the default behavior > (not re-entrant). > > The Windows implementation uses EnterCriticalSection which *is* re-entrant. > > I'm assuming that the pthreads implementation is the correct one (calling > Mutex.lock() twice on the same mutex on a single thread should deadlock the > thread) but I wanted to verify this since the implementations seem to vary. > > -atw >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
