On Mon, Aug 17, 2009 at 2:34 AM, Christophe Grand<christo...@cgrand.net> wrote: > Hi Mark and Meikel, > > On Mon, Aug 17, 2009 at 8:15 AM, Meikel Brandmeyer <m...@kotka.de> wrote: >> >> On Aug 17, 3:23 am, Mark Volkmann <r.mark.volkm...@gmail.com> wrote: >> > Maybe it's there in case ref-set or alter was called on the Ref before >> > commute. >> > In that case, does that mean that the commute functions for that Ref >> > won't be called a second time during the commit? >> >> Just guessing here, but isn't the commute using the >> newest value of the Ref during commit. When ref-set or >> alter was used in the transaction and the transaction >> is committing, the value set with ref-set/alter *will* be >> the newest value for the Ref, so there is no need to >> recompute the value for the commute (it was done >> before and it is up-to-date). > > You're exactly right. > Mark's latest post about commute > http://groups.google.com/group/clojure/browse_thread/thread/d24e4f39351fa2fd/d5adc0c4c8a500c4 > prompted this bugfix.
Ah ... thanks for explaining that! I suspect many people are under the impression that successful transactions ALWAYS call their commute functions a second time during the commit so while the new strategy makes sense, it may be a new idea to some. -- R. Mark Volkmann Object Computing, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
