Termite fork for the Black Hole module system
Switch branches/tags
Nothing to show
Pull request Compare This branch is even with per-gron:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Termite is Copyright 2005-2008 by Guillaume Germain
(guillaume.germain@gmail.com),  All Rights Reserved.

Termite is released under the same license as Gambit itself, 
see the LICENSE file.

* See the 'INSTALL' file for installation instructions. *

The current code should be considered as beta quality.  That is,
some of it isn't yet implemented using a very good style, might
contains some bug, will probably change in the near future, and the
interaction with Gambit might be a little 'rough' for now.

Don't hesitate to bug me (guillaume.germain@gmail.com) if something
doesn't work as it should, if you have questions or if you have
feature requests.


Here is some incomplete documentation about the system.

Some Notes

See "examples/start1.sh" for a minimal Termite program.

The global environment should be the same on every node, because it
isn't included in the serialization of ojects.

One should avoid to make references to unserializable objects in
closures and continuations, else things will fail.

The programs should not use mutations.  Instead, rely on the fact that
passing messages around /is/ a representation of mutable state.  See
"examples/cons.scm" for an example.  Still, mutable data structures
can be hidden behind processes with some care.  Have a look at
'data.scm' for examples.

To stay in the "spirit" of Termite, one should not use SET!, SET-CAR!,
SET-CDR!, VECTOR-SET!, STRING-SET! and similar functions.  Better
integration in the future with Gambit might prevent those forms and
functions from being available.


NODE -> node ID
(make-node ip-address tcp-port#)

TAG -> universally unique identifier

Functions and special forms:

(node-init node)

Necessary to initialize the system.

(spawn thunk)

Start a new process executing the 'body' code and return its PID.

(spawn-link thunk)

Start a new process executing the 'body' code and linking that process
to the current one and return its PID.

(remote-spawn node thunk)

Spawn a new thunk on a remote node and return its PID.


Get the PID of the running process.


Get the current node we're executing on.

(! pid message)
Send message to process.

(? [timeout [default-value]])

Receive a message, block for 'timeout' seconds if no messages.  An
exception will be raised if no default-value is specified.

(?? pred? [timeout [default-value]])
Receive a message for which (pred? message) is true.

  (pattern                . code)
  (pattern (where clause) . code)
  (after   seconds        . code))

Selectively receive a message that match a pattern, and destructure
it.  The last clause can optionally be a 'timeout' clause, with code
to execute if no messages received after a certain amount of time.

(!? pid message [timeout [default-value]])

Remote procedure call (or synchronous message).  This requires
doing something like:

  ((from token message) (! from (list token reply)))


Nicely terminate the execution of the current process.

(terminate! pid)

Forcefully terminate the execution of a local process.