On Nov 4, 1:22 pm, "Raoul Duke" <[EMAIL PROTECTED]> wrote:
> hi,
>
> > Though I don't know much about TMs, I will grant that I have not
> > actually seen such tools for TMs, so your argument probably still
> > holds, but I don't think it will hold forever.
>
> it is an interesting thing: the ecosystem of tools and things in the
> crappy shared mutable state world is large and advanced, especially if
> you have $$$ to throw at the problem (e.g. Azul's tools). which might
> make it harder for the new idea to get fast and wide adoption. still,
> one can hope that somehow the time + energy + resources somehow get
> applied to making TM tools.
>
> sincerely.
>
> p.s. in java you can write a little thread which detects deadlock in
> any other threads, so you can see it right away. we have such a thing
> in our server code at the moment.
Once detected, a deadlock can still be a bear to reproduce/debug, and
often does not appear until the worst possible time - production.
What's even more insidious is the memory not accessed under a lock
that should have been, and the ensuing corruption.
Contrast this with STM+refs, where there is no avoiding using
transactions for writes. As far as livelock, if you get it to happen
it is usually due to long-running transactions competing with short
ones, and you can readily see/reproduce it under test loads.
Rich
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
