I wrote a transaction-enabled database in perl 5, using fork()
for my multithreading and flock() for my mutexes. It continues
to work just fine.
Threading gives us mutexes. Are you just saying that
every variable should have its own mutex, and perl's = assignment
operator should implicitly set the mutex?
Giving every variable its own mutex would mean we could have
greater control if needed --- something like flock(SH|EX|NB|UN)
semantics on anything that can be an Lvalue.
How about rewriting it as an extension to flock() involving mutexes
and sending it to perl6-language?
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
Damian Conway for president
