Article View: comp.sys.transputer
Article #1732Re: Dynamic Memory Allocation (was Re: Why Occam3 probably won't be recursive)
From: Conor O'Neill
Date: Fri, 20 Nov 1992 14:01
Date: Fri, 20 Nov 1992 14:01
19 lines
1707 bytes
1707 bytes
In article <BxyB6I.LLF@research.canon.oz.au> andy@research.canon.oz.au (Andy Newman) writes: > Yes we used CHAN OF ANY - it allowed our configuration langauage and >communications system work! The two element vector holds the "to" >channel and the "from" channel used to perform the RPC with the memory >allocator process (this use exposed a limitation in the compiler, it >assumed all channels in a vector were used in the same "direction") This isn't a limitation of the _compiler_, it is a limitation of the language: page 76 of the occam reference manual says that a channel parameter may not be used for both input and output in a procedure. This is so that an implementation can just remember that it's either an `input channel array' or an `output channel array' for usage checking, without having to keep a bit vector for each element. It also means that arrays of unknown size are treated similarly. --- 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".
Technical Details
Message-ID:
<1992Nov20.140141.4279@titan.inmos.co.uk>Path:
arc1-ca.pugleaf.net!sparky!uunet!inmos!titan.inmos.co.uk!newsReferences:
<1992Nov11.033835.21118@netcom.com> <2225@eagle.ukc.ac.uk> <dbc.722086651@bill> <BxyB6I.LLF@research.canon.oz.au>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.transputer Path: arc1-ca.pugleaf.net!sparky!uunet!inmos!titan.inmos.co.uk!news From: conor@lion.inmos.co.uk (Conor O'Neill) Subject: Re: Dynamic Memory Allocation (was Re: Why Occam3 probably won't be recursive) Message-ID: <1992Nov20.140141.4279@titan.inmos.co.uk> Keywords: Occam3 recursive, no Sender: news@titan.inmos.co.uk Reply-To: conor@inmos.co.uk (Conor O'Neill) Organization: INMOS Limited, Bristol, UK. References: <1992Nov11.033835.21118@netcom.com> <2225@eagle.ukc.ac.uk> <dbc.722086651@bill> <BxyB6I.LLF@research.canon.oz.au> Date: Fri, 20 Nov 1992 14:01:41 GMT Lines: 19