[Oberon] Clarifying type compatibility in Oberon-07

[Luca Boasso]

I am afraid the frame pointer is really needed.

On Thu, Oct 12, 2017 at 8:51 AM, Andreas Pirklbauer <
andreas_pirklbauer at yahoo.com> wrote:

> > I forgot to add that this approach of course invalidates > the stack
> pointer (SP) itself. So one would need to find > a different way in fact.
> One option would be this:
>
> For leaf procedures (i.e. procedures which do not themselves
> call other procedures), the procedure NEW(a, size) can freely
> use the unused stack space that comes after current stack frame
> - it is not used anyway, so it does no harm to place data there.
>
> For non-leaf procedures (i.e. procedures that *do* call other
> procedures), you insert an instruction that adjusts the SP by
> the total amount of the allocations so far just before the
> other procedure is called, and readjust it when it returns.
>
> But as I said, I haven’t thought more deeply about this..
>
>
>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20171012/de036b26/attachment.html>