If you have to acquire multiple concurrent locks(*), always acquire the locks in the same order
Yes, yes, yes, but you don't have that option if the language does locking automatically for you - and you may not be aware that it's actually locking, do you?For the first post in this thread, I got the impression that you want Perl to automatically lock a variable whenever its being changed. Now, you can't simultaneously take this out of the hands of the programmer, and make her responsible for the order in which locking occurs.
In reply to Re^7: A faster?, safer, user transparent, shared variable "locking" mechanism.
by Anonymous Monk
in thread A faster?, safer, user transparent, shared variable "locking" mechanism.
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |