🚀 go-pugleaf

This is the official INMOS position on occam development.

PLEASE do not e-mail me about this; I am too busy.

INMOS OCCAM POSITION
====================

13th May 1992.

INMOS are fully committed to supporting the occam programming language,
and believe that for important classes of application occam 2 is the best
language for its customers to use.

The advanced development tools including an X-windows based debugger,
a profiler and a message routing configurer will all support occam 2
programming.

An occam 2 toolset for the T9000 will be available when the T9000 is available.
This will be exactly source compatible with the occam 2 system in the current
occam 2 toolset.  At the configuration level only the hardware description
will need changing to describe the T9000 hardware, the rest of the
configuration description will be exactly the same.

INMOS expects to release an optimising occam 2 compiler with full dataflow
optimisations in 1993.  In this release the occam 2 language will be
extended to support the following new features :-

 - User defined types
 - Records
 - Remove requirement for explicitly typing literals
 - Allow arithmetic on BYTE types
 - Allow FUNCTIONs to return fixed length arrays
 - Permit the dropping of FROM and FOR in segments of arrays

This represents the first phase of the occam 3 development based on
Geoff Barrett's draft language specification.

INMOS is also planning a longer term compiler development programme based on
ANDF technology.  A second phase of development addressing modularity
and sharing will be undertaken in the context of this development and will
lead to the availability of native occam 3 compilers for a wide range of
different computer architectures.

Signed: Ian Pearson, David May, Tony Debling.


---
Conor O'Neill, Software Group, INMOS Ltd., UK.
UK: conor@inmos.co.uk		US: conor@inmos.com
"It's state-of-the-art" "But it doesn't work!" "That is the state-of-the-art".