db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
@InProceedings{Welch13a,
title = "{L}ife of occam-{P}i",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
author= "Welch, Peter H.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
editor= "Welch, Peter H. and Barnes, Frederick R. M. and Broenink, Jan F. and Chalmers, Kevin and Pedersen, Jan Bækgaard and Sampson, Adam T.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
pages = "293--318",
booktitle= "{C}ommunicating {P}rocess {A}rchitectures 2013",
isbn= "978-0-9565409-7-3",
year= "2013",
month= "nov",
abstract= "This paper considers some questions prompted by a brief
review of the
history of computing. Why is programming so
hard? Why is concurrency
considered an
\textquotedbladvanced\textquotedbl subject? What's the
matter with Objects?
Where did all the Maths go? In
searching for answers, the paper looks
at some concerns over
fundamental ideas within object orientation (as
represented
by modern programming languages), before focussing on
the
concurrency model of communicating processes and its
particular
expression in the occam family of languages. In
that focus, it looks
at the history of occam, its underlying
philosophy (Ockham's Razor),
its semantic foundation on
Hoare's CSP, its principles of process
oriented design and
its development over almost three decades into
occam-pi
(which blends in the concurrency dynamics of
Milner's
pi-calculus). Also presented will be an urgent need
for
rationalisation - occam-pi is an experiment that has
demonstrated
significant results, but now needs time to be
spent on careful review
and implementing the conclusions of
that review. Finally, the future
is considered. In
particular, is there a future?"
}