occam (programming language)
|Stable release||2.1 (official), 2.5 (unofficial), 3 (not fully implemented) / 1988+|
|Influenced by||Communicating Sequential Processes|
occam is a concurrent programming language that builds on the Communicating Sequential Processes (CSP) process algebra, and shares many of its features. It is named after William of Ockham of Occam's Razor fame.
occam is an imperative procedural language (such as Pascal). It was developed by David May and others at INMOS, advised by Tony Hoare, as the native programming language for their transputer microprocessors, but implementations for other platforms are available. The most widely known version is occam 2; its programming manual was written by Steven Ericsson-Zenith and others at INMOS.
In the following examples indentation and formatting are critical for parsing the code: expressions are terminated by the end of the line, lists of expressions need to be on the same level of indentation. This feature, named the off-side rule, is also found in other languages such as Haskell and Python.
Communication between processes work through named channels. One process outputs data to a channel via "!" while another one inputs data with "?". Input and output will block until the other end is ready to accept or offer data. Examples (c is a variable):
keyboard ? c
screen ! c
SEQ introduces a list of expressions that are evaluated sequentially. This is not implicit as it is in most other programming languages. Example:
SEQ x := x + 1 y := x * x
PAR begins a list of expressions that may be evaluated concurrently. Example:
PAR p() q()
ALT specifies a list of guarded commands. The guards are a combination of a boolean condition and an input expression (both optional). Each guard for which the condition is true and the input channel is ready is successful. One of the successful alternatives is selected for execution. Example:
ALT count1 < 100 & c1 ? data SEQ count1 := count1 + 1 merged ! data count2 < 100 & c2 ? data SEQ count2 := count2 + 1 merged ! data status ? request SEQ out ! count1 out ! count2
This will read data from channels c1 or c2 (whichever is ready) and pass it into a merged channel. If countN reaches 100, reads from the corresponding channel will be disabled. A request on the status channel is answered by outputting the counts to out.
occam 1 (released 1983) was a preliminary version of the language which borrowed from David May's work on EPL and Tony Hoare's CSP. This supported only the VAR data type, which was an integral type corresponding to the native word length of the target architecture, and arrays of only one dimension.
occam 2 is an extension produced by INMOS Ltd in 1987 that adds floating-point support, functions, multi-dimensional arrays and more data types such as varying sizes of integers (INT16, INT32) and bytes.
With this revision, occam became a language capable of expressing useful programs, whereas occam 1 was more suited to examining algorithms and exploring the new language (however, the occam 1 compiler was written in occam 1, so there is an existence proof that reasonably sized, useful programs could be written in occam 1, despite its limitations).
occam 2.1 was the last of the series of occam language developments contributed by INMOS. Defined in 1994, it was influenced by an earlier proposal for an occam 3 language (also referred to as "occam91" during its early development) created by Geoff Barrett at INMOS in the early 1990s. A revised Reference Manual describing occam 3 was distributed for community comment, but the language was never fully implemented in a compiler.
occam 2.1 introduced several new features to occam 2, including:
- Named data types (DATA TYPE x IS y)
- Named Records
- Packed Records
- Relaxation of some of the type conversion rules
- New operators (e.g. BYTESIN)
- Channel retyping and channel arrays
- Ability to return fixed-length array from function.
For a full list of the changes see Appendix P of the INMOS occam 2.1 Reference Manual.
occam-π is the common name for the occam variant implemented by later versions of KRoC, the Kent Retargetable occam Compiler. The addition of the symbol "π" (pi) to the occam name is an allusion to the fact that KRoC occam includes several ideas inspired by the Pi-calculus. It contains a significant number of extensions to the occam 2.1 compiler, for example:
- Nested protocols
- Run-time process creation
- Mobile channels, data, and processes
- Protocol inheritance
- Array constructors
- Extended rendezvous
- INMOS (1995-05-12). occam 2.1 Reference Manual (PDF). SGS-Thomson Microelectronics Ltd. INMOS document 72 occ 45 03
- INMOS (1984). occam Programming Manual. Prentice-Hall. ISBN 0-13-629296-8.
- Ericsson-Zenith (1988). occam 2 Reference Manual. Prentice-Hall. ISBN 0-13-629312-3.
- Geoff Barrett and Steven Ericsson-Zenith (1992-03-31). occam 3 Reference Manual (PDF). INMOS. Retrieved 2008-03-24.
- Fred Barnes and Peter Welch (2006-01-14). "occam-pi: blending the best of CSP and the pi-calculus". Retrieved 2006-11-24.
- Communicating Process Architectures 2007 - WoTUG-30. IOS Press. 2007. pp. 513 pages. ISBN 978-1-58603-767-3. 
- Communicating Process Architectures 2006 - WoTUG-29. IOS Press. 2006. pp. 391 pages. ISBN 978-1-58603-671-3. 
- Communicating Process Architectures 2005 - WoTUG-28. IOS Press. 2005. pp. 405 pages. ISBN 978-1-58603-561-7. 
- Kerridge, Jon; (ed.) (1993). Transputer and Occam Research: New Directions. IOS Press. pp. 253 pages. ISBN 0-8247-0711-7.
- Roscoe, A W; C A R Hoare (1986). The Laws of Occam Programming. Programming Research Group, Oxford University.
- Egorov, A., Technical University - Sofia, (1983-2011)Записки по Компютърни архитектури
- The occam-π programming language
- WoTUG: occam, information, implementations
- The Transterpreter, an occam virtual machine
- KRoC: Kent Retargetable occam Compiler
- occam tutorial
- Internet Parallel Computing Archive: occam (Documentation and implementations but no longer maintained)
- Tock occam compiler
- RMoX, an operating system written in occam-π
- LuaCSP, a framework that allows you to create Occam-like Lua-based programming language embeddable in your application.