Think about deadlock, extra overhead, and time taken to take the lock.
If a set of variables should be locked as a unit only one mutex should
be assigned.
What to do about overlapping members....
<chaim>
>>>>> "DLN" == David L Nicol <[EMAIL PROTECTED]> writes:
DLN> I wrote a transaction-enabled database in perl 5, using fork()
DLN> for my multithreading and flock() for my mutexes. It continues
DLN> to work just fine.
DLN> Threading gives us mutexes. Are you just saying that
DLN> every variable should have its own mutex, and perl's = assignment
DLN> operator should implicitly set the mutex?
DLN> Giving every variable its own mutex would mean we could have
DLN> greater control if needed --- something like flock(SH|EX|NB|UN)
DLN> semantics on anything that can be an Lvalue.
DLN> How about rewriting it as an extension to flock() involving mutexes
DLN> and sending it to perl6-language?
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
