http://forums.pragprog.com/forums/27/topics/298 en-us 60 <p>My understanding (Joe, correct me if I am wrong), is that the term Side effect is used in the book to mean anything that alters state outside of the current function being executed.</p> <p>All Variables in Erlang are either bound or unbound. Once bound through matching in an expression an Erlang Variable cannot be changed. What appears to be an assignment operator (the &#8221;=&#8221; sign) is in actual fact a constraint expression declaring the left and right hand sides of the expression to be equal.</p> <p>Writing X = 1 followed by X = 2 will fail on X = 2 because X has already been constrained to equal 1 by X = 1. This pattern matching mechanism requires rethinking the design of state and variables in a program. <span class="caps">IMHO</span>, the end result is more comprehensible code that is easier to reason about and explain to others.</p> <p>In Erlang an expression cannot directly modify the state of another function or even other expressions in the same scope. All such modifications are explicitly made through the interpretation of messages or function parameters. By Chapter 3 you have not gotten to see Message Passing or Concurrency. It should hopefully be clearer at that point.</p> <p>I check this board frequently so please post your questions here. I will do my best to help :)</p> Wed, 02 Apr 2008 02:57:18 -0000 forums.pragprog.com:27:298:2522 Alain O'Dea http://forums.pragprog.com/forums/27/topics/298 <p>I already finish 3 chapters, but still don&#8217;t understand what mean that expression? I know only side effect in C++ or other imperative languages.</p> Thu, 06 Mar 2008 22:41:10 -0000 forums.pragprog.com:27:298:2395 Alexey Kuznetsov http://forums.pragprog.com/forums/27/topics/298