jimfcarroll/xbmc — comment on commit fa29541976001a729f84b4713b34b14e36295582
File:  line 0
By FernetMenta:

The error handler CheckStatus writes to the display state variable so in this case the DisplaySection lock is always nested in DecoderSection. Yes, I agree, for the other methods it is not required to do the nesting. I just wanted to follow a consistent approach and having DecoderSection protect the entire object.

I am not facing any performance issues with the locks. Using CSharedLock insted of the SharedSection directly prevents the programmer from forgetting to unlock, right? And that is what I am talking about. What else can the framework provide to make life easier at the higher levels. The single threaded design of the video player is exhausted and the bottle necks can only be removed by introducing additional threads and locks.

`Does that remove the need for a reentrant SharedSection?`
I just thought it would be nice to have.
What concepts can better hide the complexity of threads and locks from the application level? Or at least make it less error-prone.