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 [2008/03/13 16:23] – * tvcutsem | at:tutorial:actors [2008/08/01 14:45] – * tvcutsem | ||
---|---|---|---|
Line 26: | Line 26: | ||
}; | }; | ||
}; | }; | ||
- | >>< | + | >>< |
</ | </ | ||
Line 70: | Line 70: | ||
}; | }; | ||
}; | }; | ||
- | >>< | + | >>< |
</ | </ | ||
Line 112: | Line 112: | ||
}; | }; | ||
}; | }; | ||
- | >>< | + | >>< |
</ | </ | ||
Line 196: | Line 196: | ||
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 '' | 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 '' | ||
+ | |||
+ | More information pertaining to the API of the futures language module can be found in the [[: | ||
==== Working with Unresolved Futures ==== | ==== Working with Unresolved Futures ==== | ||
Line 204: | Line 206: | ||
The solution proposed in the [[http:// | The solution proposed in the [[http:// | ||
+ | |||
+ | As an example of a pipeline of message sends, consider the following code: | ||
+ | |||
+ | < | ||
+ | def booleanFuture := remoteObject< | ||
+ | booleanFuture< | ||
+ | ... | ||
+ | } ifFalse: { | ||
+ | ... | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In this example, the message '' | ||
==== Working with Resolved Futures ==== | ==== Working with Resolved Futures ==== | ||
Line 271: | Line 286: | ||
</ | </ | ||
- | Finally, it is useful to know that '' | + | Finally, it is useful to know that '' |
< | < | ||
Line 318: | Line 333: | ||
An actor in AmbientTalk is primarily a //host// for regular objects. It is equipped with a message queue to receive asynchronous messages sent to one of its objects. The mirrors on these objects have corresponding meta-level operations such as '' | An actor in AmbientTalk is primarily a //host// for regular objects. It is equipped with a message queue to receive asynchronous messages sent to one of its objects. The mirrors on these objects have corresponding meta-level operations such as '' | ||
- | Some operations, such as creating and sending asynchronous messages are useful to reify at the //actor level//. With such a reification, | + | Some operations, such as creating and sending asynchronous messages are useful to reify at the //actor level//. With such a reification, |
- | Overriding the actor' | + | Overriding the actor' |
< | < | ||
- | def oldmirror := actor.install: (extend: actor with: { | + | def actor := reflectOnActor(); |
+ | def oldmirror := actor.becomeMirroredBy: (extend: actor with: { | ||
def send(msg) { | def send(msg) { | ||
log(msg); | log(msg); | ||
Line 331: | Line 347: | ||
</ | </ | ||
- | Notice that, in this example, the new metaobject protocol is an extension of the old protocol. This enables it to invoke its parent' | + | Notice that, in this example, the new metaobject protocol is an extension of the old protocol. This enables it to invoke its parent' |
< | < |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag