On Wed, Sep 16, 2009 at 6:13 AM, Krukow <karl.kru...@gmail.com> wrote:
> On Sep 15, 10:23 pm, Mark Volkmann <r.mark.volkm...@gmail.com> wrote: > > I think the problem is that you only ensure one of the Refs. If you > > want to make sure that a condition between multiple Refs isn't > > violated, you need to sure all of them. Otherwise other transactions > > will be free to modify the Refs that aren't ensured. > > My reasoning is that since I am writing to one ref and ensuring the > other, I don't need to also ensure the ref I am writing to. > And you are right: you don't need to ensure the other ref since you are writing to it. This bug was fixed on august 28: http://github.com/richhickey/clojure/commit/b942b1758040f3f96dacb7e0cecb148913ba5f1e Christophe -- Professional: http://cgrand.net/ (fr) On Clojure: http://clj-me.blogspot.com/ (en) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
