aboutsummaryrefslogtreecommitdiff
path: root/chapter/3
diff options
context:
space:
mode:
authorHeather Miller <heather.miller@epfl.ch>2017-01-03 17:58:37 +0100
committerHeather Miller <heather.miller@epfl.ch>2017-01-03 17:58:37 +0100
commit21cddf809d02a674f1fac59ccc5dfb3adac3bab2 (patch)
treec9ff1b135b662223ef03ef07293efed716227efd /chapter/3
parentc4958a50b1555c8b40e3fde26832d0f774693b47 (diff)
Moar faceliftfacelift
Diffstat (limited to 'chapter/3')
-rw-r--r--chapter/3/message-passing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/chapter/3/message-passing.md b/chapter/3/message-passing.md
index 3a27a40..25757e7 100644
--- a/chapter/3/message-passing.md
+++ b/chapter/3/message-passing.md
@@ -100,7 +100,7 @@ Splitting concerns into multiple pieces allows for the programmer to have an eas
This flexibility turns out to be a highly discussed advantage which continues to be touted in modern actor systems.
-## Rosette
+### Rosette
Rosette was both a language for concurrent object-oriented programming of actors, as well as a runtime system for managing the usage of and access to resources by those actors. Rosette {% cite Tomlinson:1988:ROC:67387.67410 --file message-passing %} is mentioned throughout Agha's _Concurrent Object-Oriented Programming_, {% cite Agha:1990:COP:83880.84528 --file message-passing %} and the code examples given in the paper are written in Rosette. Agha is even an author on the Rosette paper, so its clear that Rosette is foundational to the classic actor model. It seems to be a language which almost defines what the classic actor model looks like in the context of concurrent object-oriented programming.