at:tutorial:actors
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:tutorial:actors [2007/04/01 12:05] – added tvcutsem | at:tutorial:actors [2007/04/06 20:00] – added tvcutsem | ||
---|---|---|---|
Line 38: | Line 38: | ||
AmbientTalk, | AmbientTalk, | ||
- | Far references, like the reference stored in the variable '' | + | Far references, like the reference stored in the variable '' |
Hence, given the example above, the method '' | Hence, given the example above, the method '' | ||
Line 47: | Line 47: | ||
</ | </ | ||
- | async messages, parameter passing, | + | The above code is simple enough to understand: the '' |
+ | |||
+ | But what happens when the method to invoke asynchronously has parameters that need to be passed. How does parameter passing work in the context of inter-actor message sending? The rules are simple enough: | ||
+ | - Objects and closures are always passed **by reference** | ||
+ | - Native data types like numbers, text, tables, ... are always passed **by copy** | ||
+ | |||
+ | Generally speaking, any object that encapsulates a lexical scope is passed by reference, because passing such an object by copy would entail passing the entire lexical scope by copy - a costly operation. Objects without a lexical scope, such as methods, can be copied without having to recursively copy any scope. | ||
+ | |||
+ | When an object is passed by reference, we mean that the formal parameter of a method will be bound to a far reference to the original object. When it is passed by copy, the formal parameter will be bound to a local copy of the object. For example, consider the following '' | ||
+ | |||
+ | < | ||
+ | >def calculator := actor: { | ||
+ | def add(x, | ||
+ | customer< | ||
+ | }; | ||
+ | }; | ||
+ | >>< | ||
+ | </ | ||
+ | |||
+ | The '' | ||
+ | |||
+ | < | ||
+ | > | ||
+ | def result(sum) { | ||
+ | system.println(" | ||
+ | }; | ||
+ | }); | ||
+ | >> | ||
+ | </ | ||
+ | |||
+ | Because of the parameter passing | ||
+ | |||
+ | < | ||
+ | sum = 3 | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | The parameter passing semantics just described lead to a model where the only references that cross actor boundaries are far references. In combination with the message sending semantics described previously, this guarantees that asynchronous messages are the only type of messages that can cross actor boundaries, ensuring that concurrent (and as will be shown later, also distributed) communication is strictly asynchronous. In such a model, deadlocks cannot occur (an actor is never blocked) and race conditions within one single actor can never occur. These properties significantly reduce the complexity of concurrent programs. | ||
+ | </ | ||
=== Isolates === | === Isolates === | ||
- | isolate stripe, by-copy, scoping rules, no external method | + | The parameter passing semantics defined above rule out any possibility for an object to be passed by copy. The reason for this semantics is that objects encapsulate a lexical scope, and parameter passing an object by-copy would require the entire lexical scope to be parameter-[assed as well. |
+ | |||
+ | To enable objects to be passed by copy between actors, a special type of objects is introduced. These objects are called **isolates** because they are // | ||
+ | |||
+ | < | ||
+ | >def complexNumber := isolate: { | ||
+ | def re; // assume cartesian coordinates | ||
+ | def im; | ||
+ | def init(re,im) { | ||
+ | self.re := re; | ||
+ | self.im := im; | ||
+ | }; | ||
+ | def +(other) { | ||
+ | self.new(re+other.re, | ||
+ | }; | ||
+ | }; | ||
+ | >>< | ||
+ | </ | ||
+ | |||
+ | The '' | ||
+ | |||
+ | An isolate differs from a regular object as follows: | ||
+ | - it has **no** access to its surrounding lexical scope; this means that an isolate only has access to its local fields and methods. An isolate does have access to the global lexical scope of its actor. | ||
+ | - it is parameter-passed | ||
+ | - external method | ||
+ | |||
+ | Returning to the calculator example, the calculator can now add complex numbers locally and send (a copy of) the resulting complex number back to the customer: | ||
+ | |||
+ | < | ||
+ | > | ||
+ | complexNumber.new(1, | ||
+ | complexNumber.new(2, | ||
+ | object: { | ||
+ | def result(sum) { | ||
+ | system.println(" | ||
+ | }; | ||
+ | }); | ||
+ | >> | ||
+ | sum=(3,3) | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | A word of warning: isolates are objects that are copied freely between actors. As a result, they should be objects whose actual object identity is of little importance. Usually, the identity of by-copy objects is determined by the value of some of the object' | ||
+ | < | ||
+ | def ==(other) { | ||
+ | (re == other.re).and: | ||
+ | } | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | It is important to note that an isolate has no access whatsoever to its encompassing scope. The following code results in an exception: | ||
+ | |||
+ | < | ||
+ | >def x := 1; | ||
+ | def adder := isolate: { | ||
+ | def add(n) { x + n }; | ||
+ | }; | ||
+ | adder.add(3) | ||
+ | >> | ||
+ | origin: | ||
+ | at adder.add(3) | ||
+ | </ | ||
+ | |||
+ | Sometimes it is useful to initialize an isolate with the values of lexically visible variables. In that case, AmbientTalk allows the programmer to specify which lexical variables should be //copied into// the isolate itself, such that the isolate has its own, local copy of the variable. Lexical variables that need to be copied like this are specified as formal parameters to the closure passed to the '' | ||
+ | |||
+ | < | ||
+ | >def x := 1; | ||
+ | def adder := isolate: { |x| | ||
+ | def add(n) { x + n }; | ||
+ | }; | ||
+ | adder.add(3) | ||
+ | >>4 | ||
+ | </ | ||
+ | |||
+ | === Futures === | ||
+ | |||
+ | As you may have noticed previously, asynchronous message sends do not return any value (that is, they return '' | ||
+ | |||
+ | The most well-known language feature to reconcile return values with asynchronous message sends is the notion of a //future//. Futures are objects that represent return values that may not yet have been computed. Once the asynchronously invoked method has completed, the future is replaced with the actual return value, and objects that referred to the future transparently refer to the return value. | ||
+ | |||
+ | Using futures, it is possible to re-implement the previous example of requesting our calculator actor to add two numbers as follows: | ||
+ | |||
+ | < | ||
+ | def sum := calculator< | ||
+ | </ | ||
+ | |||
+ | Futures are a frequently recurring language feature in concurrent and distributed languages (for example, in ABCL, the actor-based concurrent language). They are also commonly known by the name of // | ||
+ | |||
+ | To enable futures, it suffices to import the futures module and to enable it, as follows: | ||
+ | |||
+ | < | ||
+ | import / | ||
+ | enableFutures(true); | ||
+ | </ | ||
+ | |||
+ | The first statement imports the futures module into the current lexical scope. This enables you as a developer to use some additional language constructs exported by the futures module, as will be explained later. The second statement enables the futures behaviour, causing any asynchronous message send to return a future rather than '' | ||
=== Actor Mirrors === | === Actor Mirrors === |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag