Subj : Re: recursive mutexes
To   : comp.programming.threads
From : doug
Date : Mon May 16 2005 09:24 am


"Chris Thomasson" <_no_damn_spam_cristom@_no_damn_comcast.net_spam> wrote in 
message news:2pOdndaD_5x9qRXfRVn-ow@comcast.com...
>> When someone questions you, you answer rather indignantly.  Each post 
>> sounds as though you've read the next chapter in your threading book and 
>> want to share.
>
> It sure does. He seems a bit inexperienced...
>

It's good that he gave it a stab, but I don't understand his reluctance to 
read up on existing 'well-known' practises in this area and his 
unwillingness to listen to others.
For the current code I'm working on, it would take me several hours, perhaps 
days, to type in the lock information his tool requires.  That's not to 
mention the fact that threads are created dynamically, and their behaviour 
is unpredictable (I see nothing in his tool that allows you to grab this 
lock OR that lock, depending on some state.).  All he's done is specialise 
hierarchical locking for simplified scenarios.

.