On Wed, 7 Jun 2000, Christoph Reichenbach wrote:
> Hi,
>
> > I've encountered a problem with our handling of the stack. I must admit
> > I'm very surprised that this bug hasn't surfaced before: When doing
> > multiple sends, each send must not frob the stack of the previous one.
>
> So all of the allocations accumulate, and the last of the methods sent for
> in the list frees all of the memory allocated by its predecessors?
Yes, apparently. That may be the reason why it's called the "link" opcode
- because it allows send calls to share each other's temp variables. But
as I said, this feature is rarely used. Again, gamefile.sh may be your
best bet for experimentation.
>
> llap,
> Christoph
>
Lars
