>> Yeah, clever, and basically the same as the eventual fix I had for >> JRuby >> since it gives each thread its own counter. I think the primary rule >> here is that don't expect any sort of unsynchronized, uncontrolled >> updates to the same shared resource to either behave the way you >> want or >> perform the way you want. > > It may be a bit off-topic, but it's interesting how this argues for > immutable data structures and Erlang's concurrency model.
I guess once you're into concurrency, everything argues for immutable data structures. It's also nice to see how this fits with Gilad Brachas arguments against the Java 'static' keyword (which allows mutable structures to be shared implicitly between threads), as Charles already noted. Regards, Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
