This commit is contained in:
Tony Garnock-Jones 2013-05-10 17:39:26 -04:00
parent 3a4e21581b
commit 604e7d0373
3 changed files with 8 additions and 10 deletions

View File

@ -81,6 +81,10 @@ structures.
actions the process wishes to perform. See @secref{Actions} for the
possible actions a process can take.
Note that the result of an event handler function is actually a
@racket[Transition] structure; the actual Typed Racket type of event
handlers is @racket[TrapK], defined in @secref{handler-functions}.
@section{What is a VM?}
@deftech[#:key "vm"]{Virtual Machines (VMs)} are simply a collection
@ -135,6 +139,8 @@ Roles have three parts:
]
@section[#:tag "messages-and-topics"]{Messages and Topics}
@deftech{Messages} are simply Racket data structures. They can be any
value for which @racket[equal?] is defined, any @racket[#:prefab]
structure, most @racket[#:transparent] structures, or any non-object

View File

@ -96,15 +96,6 @@ its state type).
}
@section{Constructing topics and roles}
As previously mentioned, @tech{topics} are ordinary Racket values
which may have embedded wildcards. The identifier @racket[?] produces
a fresh wildcard value for use in topic patterns.
For example,
TODO
@section{Constructing transitions}
**** transition, transition:, transition/no-state
**** cons-trees of actions; null, false, void; use of (when)
@ -113,6 +104,7 @@ TODO
@section{Actions}
**** Communication-related
***** endpoint, endpoint:
[#:tag "endpoint-dsl"]
***** delete-endpoint
***** send-message
***** send-feedback

View File

@ -18,7 +18,7 @@ the @emph{system call interface} of a Unix-like operating system. The
@secref{high-level-interface} corresponds to the @emph{C library
interface} of a Unix-like operating system.
@section{Handler Functions}
@section[#:tag "handler-functions"]{Handler Functions}
Each @deftech{handler function} is always associated with a particular
@tech{endpoint}, registered with the VM via