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/06 20:50] – tvcutsem | at:tutorial:actors [2007/04/07 17:27] – tvcutsem | ||
---|---|---|---|
Line 36: | Line 36: | ||
==== Asynchronous Message Sending ==== | ==== Asynchronous Message Sending ==== | ||
- | AmbientTalk, | + | AmbientTalk, |
Far references, like the reference stored in the variable '' | Far references, like the reference stored in the variable '' | ||
Line 50: | Line 50: | ||
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: | 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** | + | - Objects and closures are always passed **by far reference** |
- Native data types like numbers, text, tables, ... are always passed **by copy** | - Native data types like numbers, text, tables, ... are always passed **by copy** | ||
Line 89: | Line 89: | ||
==== Isolates ==== | ==== Isolates ==== | ||
- | 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 | + | 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-passed |
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 // | 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 // |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag