Paper Details

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"

%T Working towards a successor to occam
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
%A Ian R. East
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"
%E Alan G. Chalmers, Majid Mirmehdi, Henk Muller
%B Communicating Process Architectures 2001
%X occam [1] offers features and attributes that make it unique
   among programming languages, particularly in the ease and
   security with which one may program concurrency. After a
   brief summary of occam\[rs]s strengths, possible additional
   features are discussed, including recursion, source code
   modularity, exception response, and the automatic avoidance
   of deadlock. Consideration is then given to the inclusion of
   passive (\[rs]data\[rs]) objects and the possibility of
   their movement between processes. Transfer primitives are
   proposed, alongside assignment and communication. Discussion
   is presented with regard to the potential for a new
   programming language, building on occam, while preserving
   its security and simplicity.

If you have any comments on this database, including inaccuracies, requests to remove or add information, or suggestions for improvement, the WoTUG web team are happy to hear of them. We will do our best to resolve problems to everyone's satisfaction.

Copyright for the papers presented in this database normally resides with the authors; please contact them directly for more information. Addresses are normally presented in the full paper.