> Here's some exposition: http://clojure.org/concurrent_programming
I will reread it then > > >> Another question I would love to have immutability bit for pharo. >> Now if you have immutable collection then I imagine that >> - you should copy them when you want to modify them (functional) > > That happens automatically. Modification operations are functional > > e.g. f(data) -> data' > > data' is a different object than data, which remains unchanged. > Efficiently implementing this is the key, but it's been done. but do they guarante identity preservation I guess not. > > >> - I was wondering if the object that you put such immutable data >> structure should >> also be immutable > > Not necessarily - in the case of Clojure you might put a Ref/Var/Atom/ > Agent into an immutable structure, and those objects have their own > concurrency semantics as described in the link above. > > Antony Blakey > ------------- > CTO, Linkuistics Pty Ltd > Ph: 0438 840 787 > > Borrow money from pessimists - they don't expect it back. > -- Steven Wright > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
