>>>>> "JH" == Jarkko Hietaniemi <[EMAIL PROTECTED]> writes:
JH> Multithreaded programming is hard and for a given program the only
JH> person truly knowing how to keep the data consistent and threads not
JH> strangling each other is the programmer. Perl shouldn't try to be too
JH> helpful and get in the way. Just give user the bare minimum, the
JH> basic synchronization primitives, and plenty of advice.
The problem I have with this plan, is reconciling the fact that a
database update does all of this and more. And how to do it is a known
problem, its been developed over and over again.
Yes, it may be expensive, so we wouldn't go with it, but I don't want
to reject it out of hand.
Perl has full control of its innards so up until any data leaves perl's
control, perl should be able to restart any changes.
Take a mark at some point, run through the code, if the changes take,
we're ahead of the game. If something fails, back off to the checkpoint
and try the code again.
So any stretch of code with only operations on internal structures could
be made eligable for retries.
<chaim>
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
