db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
@InProceedings{TeigVannebo09,
  title =        "{N}ew {ALT} for {A}pplication {T}imers and {S}ynchronisation {P}oint {S}cheduling",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  author=        "Teig,  Øyvind and Vannebo,  Per Johan",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  editor=        "Welch, Peter H. and Roebbers,  Herman and Broenink,  Jan F. and Barnes,  Frederick R. M. and Ritson,  Carl G. and Sampson,  Adam T. and Stiles,  G. S. and Vinter,  Brian",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  pages =        "135--144",
  booktitle=     "{C}ommunicating {P}rocess {A}rchitectures 2009",
  isbn=          "978-1-60750-065-0",
  year=          "2009",
  month=         "nov",
  abstract=      "During the design of a small channel-based concurrency
     runtime system
(ChanSched, written in ANSI C), we saw that
     application timers (which
we call egg and repeat timers)
     could be part of its supported ALT
construct, even if their
     states live through several ALTs. There are
no side effects
     into the ALT semantics, which enable waiting for
channels,
     channel timeout and, now, the new application
     timers.
Application timers are no longer busy polled for
     timeout by the
process. We show how the classical occam
     language may benefit from a
spin-off of this same idea. 
     Secondly, we wanted application
programmers to be freed from
     their earlier practice of explicitly
coding communication
     states at channel synchronisation points, which
was needed
     by a layered in-house scheduler. This led us to develop
     an
alternative to the non-ANSI C \textquotedblcomputed
     goto\textquotedbl (found in gcc). Instead,
we use a
     switch/case with goto line-number-tags in a
     synch-point-table
for scheduling.  We call this table, one
     for each process, a proctor
table. The programmer does not
     need to manage this table, which is
generated with a script,
     and hidden within an \#include file."
}