Differences

This shows you the differences between two versions of the page.

--- at:tutorial:actors [2011/05/23 13:51] – tvcutsem
+++ at:tutorial:actors [2020/02/05 21:19] – elisag
@@ Line 191: / Line 191: @@
 </code>
-==== Enabling futures ====
 In AmbientTalk, futures are not native to the language. However, because of AmbientTalk's reflective infrastructure, it is possible to build futures on top of the language. The system library shipped with AmbientTalk contains exactly this: a reflective implementation that adds futures to the language kernel. This implementation can be found in the file ''at/lang/futures.at''.
+In what follows we provide an overview on how to work with futures. More information pertaining to the API of the futures language module can be found in the [[:at:tutorial:appendix#futures_and_multifutures|appendix]].
+==== Enabling futures ====
 To enable futures, it suffices to import the futures module and to enable it, as follows:
@@ Line 203: / Line 209: @@
 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 ''nil''. If ''false'' is passed to the call to ''enableFutures'', only messages annotated explicitly as ''@FutureMessage'' (or as ''@TwoWay'') will return a future.
-More information pertaining to the API of the futures language module can be found in the [[:at:tutorial:appendix#futures_and_multifutures|appendix]].
 ==== Working with Unresolved Futures ====