🚀 go-pugleaf

Recursion of occam-2 or -3

I have seen enough of stack overflow errors to appreciate the lack
of recursion in occam.

Rob Kurver writes:
> It is very well possible to introduce stack checking code during linking,
> when a call-graph of the program can be used to determine if and when
> it is possible.  This would result in ZERO overhead for a program written
> without recursion, and minimum overhead for recursive programs.  We
> are currently working on this feature in PACT Parallel C.

Ok, but you still have not removed the stack overflow!

This comes close to the discussion of exception-handling: how do
you solve that in Pact-C, and what would you recommend when stack overflow
is encountered?

If occam had been written from the philosophy that "if you don't need it,
don't use it", it definitively would have not been occam.

Is it possible to do multi-language design with the Inmos D7205 occam
toolset and your Pact C-compiler, like it is with the Inmos C-toolset?

For me as an occam-user, your parallel C (:-) is of little interest because
C is not interesting, if it were, I would not have used occam (recursive
definition: interesting but little useful(%-|)

0yvind Teig
Autronica, Trondheim, Norway