home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.transputer
- Path: sparky!uunet!inmos!titan.inmos.co.uk!news
- From: steved@lion.inmos.co.uk (Stephen Doyle)
- Subject: Re: IS Occam3 recursive?
- Message-ID: <1992Nov18.130407.12799@titan.inmos.co.uk>
- Sender: news@titan.inmos.co.uk
- Reply-To: steved@inmos.co.uk (Stephen Doyle)
- Organization: INMOS Limited, Bristol, UK.
- References: <rob.721665532@dutncp8> <MICHAEL.92Nov16185558@lucrece.uk.ac.oxford> <2292@eagle.ukc.ac.uk> <rob.722034771@dutncp8>
- Date: Wed, 18 Nov 1992 13:04:07 GMT
- Lines: 38
-
- In article <rob.722034771@dutncp8> rob@pact.nl (Rob Kurver) writes:
-
- >
- >The CSP paradigm as supported by Occam and PACT Parallel C is a very
- >powerful one, and is especially interesting with the support provided
- >by the transputer.
- >
- >Cheers. - Rob
- >
-
- Rob, you seem to have forgotten about INMOS ANSI C providing the same sort of
- CSP paradigm as your own, this obviously slipped your mind :-). I guess the
- difference boils down to whether you want an ANSI C validated compiler with
- functional additions for parallelism and communications or an ANSI C compiler
- with non-ANSI language additions for the same. I would argue (from customer
- feedback) that OCCAM tends to be used along with INMOS ANSI C as this
- provides you with a flexible environment for parallel/comms/sequential
- programming with excellent diagnostics at compile and run time.
-
- Just to cloud the issue once more INMOS' soon to be shipping new optimising C
- compiler has a specific optimisation for tail call recursion i.e.
-
- void p (int q)
- {
- ...
- return(p(...));
- }
-
- in this case the workspace of p is reused as the function recurses, also,
- nested returns are omitted so that only one return is needed no matter how many
- levels of recursion take place.
-
- Steve
-
- Steve Doyle, Software Marketing, INMOS Ltd | Tel +44 454 616616
- 1000 Aztec West |
- Almondsbury | UK: steved@inmos.co.uk
- Bristol BS12 4SQ, UK | US: steved@inmos.com
-