Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!mcsun!ukc!inmos!conor@lion.inmos.co.uk
From: conor@lion.inmos.co.uk (Conor O'Neill)
Newsgroups: comp.sys.transputer
Subject: Re:  Anarchic protocol ANY (occam2)
Message-ID: <16169@ganymede.inmos.co.uk>
Date: 21 May 91 12:53:05 GMT
References: <9105161505.AA01949@rt.el.utwente.nl>
Sender: news@inmos.co.uk
Reply-To: conor@inmos.co.uk (Conor O'Neill)
Organization: INMOS Limited, Bristol, UK.
Lines: 24

In article <9105161505.AA01949@rt.el.utwente.nl> sun@rt.eltn.utwente.nl (Johan Sunter) writes:
>    PROC process.1(CHAN OF ANY to.p2)
>      [100]BYTE buffer:
>      INT s, h1, h2:
>      SEQ
>        REAL32 r RETYPES [buffer FROM 0 FOR 4]:
>        INT    i RETYPES [buffer FROM 4 FOR 4]:
>        BOOL   b RETYPES [buffer FROM 8 FOR 1]:
>        REAL64 x RETYPES [buffer FROM 9 FOR 8]:
                                  ^^^^^^^^^^^^

Note that there is an implementation restriction in current INMOS
compilers that this RETYPES must be word-aligned.
It will be caught by a run-time check.
(Yes, I know that this example should be caught at compile-time).

This is because transputers cannot access non-word-aligned objects efficiently.



---
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".