By bloid
via debasishg.blogspot.com
Published: Aug 18 2008 / 10:32
In my last post on Scala actors, I had mentioned about the actor code being side-effect-free and referentially transparent. James Iry correctly pointed out that Scala react is side-effected, since the partial function that it takes processes a message which is neither a parameter to react nor a value in the lexical scope.
-
Clojure: Checking for a nil value in a collection
-
Inside Microsoft's Language Design Process with Luca Bolognese
-
Designing Social Interfaces: Overview and Practical Techniques
-
Maven appassembler Plugin: Dealing with Long Classpath on Windows
-
WCF RIA Services – What you need to know when creating DTO/Presentation Model
-
Pystachio lets you execute Python in modern browsers
Comments
daniel replied ago:
Quite insightful. Concurrency really is all about side-effects, but modularizing the side-effecting sections of the algorithm allows far greater maintainability because the app code itself is all pure-functional.
Voters For This Link (11)
Voters Against This Link (0)