> I'm not sure why a getValue/setValue is any different from an ='s > sign. Instability and unpredictability still results. Be they actors > or threads, neither really solves any sort of problem save perhaps > atomic updates.
My (unproven) gut feeling is that people are afraid of machine concurrency, and the removal of machine-level concurrency issues (by use of appropriate high-level abstractions) cause a belief, which is in my estimation mistaken, that you are therefor rid of *all* concurrency issues. In any case, for the record, I did not mean to imply that i agreed, overall, with the originally posted article. -- / Peter Schuller -- 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
