On Sun, May 30, 2010 at 2:39 PM, Barney Boisvert <bboisv...@gmail.com> wrote: > This purity of environment only works completely in academia, but a > very close approximation can be created that is useful for real-world > problems. Clojure (a JVM-based Lisp dialect) is an example of this, > leveraging Actors to deal with concurrent modification problems > without foisting the hassle of locking on the developer.
Clojure also implements STM natively (Software Transactional Memory - a approach which is gaining popularity lately and attempts to apply database-style transactions to memory access in applications). Scala is probably more approachable for folks familiar with Java and it too has a concurrency model based on Actors, as well as an STM implementation. Groovy also has an Actor implementation called GPars. The Groovy community is also looking at STM. Scala Actors: http://www.scala-lang.org/node/242 - Scala Actors STM: http://en.wikipedia.org/wiki/Software_transactional_memory STM in Scala: http://www.codecommit.com/blog/scala/software-transactional-memory-in-scala Groovy Actors in GPars: http://gpars.codehaus.org/Actor -- Sean A Corfield -- (904) 302-SEAN Railo Technologies, Inc. -- http://getrailo.com/ An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwoo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:334130 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
