Content deleted Content added
m Rewording |
m Sections |
||
Line 43:
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 2===
'''Occam 2''' is an extension produced by INMOS Ltd in 1987 that adds floating-point, functions and more language types like varying sizes of integers (INT16, INT32) and character types.
Line 51 ⟶ 53:
["occam 2 Reference Manual", [[INMOS]], P-H 1988, ISBN 0-13-629312-3].
===Occam 2.1===
'''Occam 2.1''' is a second enhancement to occam, produced in 1988 by [[INMOS]] Ltd. It was the last of the series language developments contributed by INMOS. Despite its "incremental" version number, it was a significant upgrade in the usefulness of the language, introducing:
Line 65 ⟶ 67:
For a full list of the changes see Appendix P of the [http://www.wotug.org/occam/documentation/oc21refman.pdf INMOS Occam 2.1 Reference Manual].
===Occam 3===
'''Occam 3''' was the name for a proposal for the next-generation occam language, created by one of the senior programmers at INMOS. A specification was created and distributed for community comment. The new language included a large number of changes, many of which were focussed at making code sharing, simultaneous development, and project reuse easier.
Line 72 ⟶ 74:
Some elements from occam 3 were introduced into the occam 2.1 compiler by other teams, and came to be known as 'occam 2.5' - as in "half-way there"!
===Occam 2.5===
'''Occam 2.5''' is the common name for the language compiled by the Kent Retargettable Occam compiler [[KRoC]]. It contains a significant number of extensions to the occam 2.1 compiler, for example:
| |||