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:40] – added tvcutsem | at:tutorial:actors [2007/04/07 17:24] – 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 253: | Line 253: | ||
}; | }; | ||
</ | </ | ||
+ | |||
+ | The '' | ||
+ | |||
+ | < | ||
+ | when: sumFuture becomes: { |sum| | ||
+ | system.println(" | ||
+ | }; | ||
+ | system.print(" | ||
+ | >> | ||
+ | </ | ||
+ | |||
+ | === Futures and Striped Messages === | ||
+ | |||
+ | Explain: | ||
+ | '' | ||
+ | '' | ||
+ | |||
+ | === Conditional Synchronisation with Futures === | ||
+ | |||
+ | explain: explicit futures using '' | ||
==== Actor Mirrors ==== | ==== Actor Mirrors ==== |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag