[lldb-dev] update Python locking refactoring

[Jim Ingham]

This looks fine.

Jim

On Oct 24, 2011, at 3:27 AM, Enrico Granata wrote:

> Hi all,
> attached to this email is an update for the patch that refactors the current implementation of locking in ScriptInterpreterPython.
> This update merges the previous version with Benjamin Kramer's refactoring. Other than that, it is the same as the previous version.
> 
> Thanks for any feedback on this.
> 
> - Enrico Granata
> 
> On Oct 20, 2011, at 6:26 PM, Enrico Granata wrote:
> 
>> Hi all,
>> attached to this email is a patch that refactors the current implementation of locking in ScriptInterpreterPython.
>> Essentially, it improves on the existing Locker class to make it feasible for use everywhere a lock on the Python interpreter is required, and makes several code changes in ScriptInterpreterPython to use Locker instances instead of replicating code for acquiring and releasing said lock.
>> This should improve maintainability and readability of code in ScriptInterpreterPython, while keeping the external behavior of the class consistent (several runs of the test suite have shown no issues).
> 
> <pylock.diff>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev