[Openmcl-devel] Re: "leaking" call-method

[Gary Byers]

On Thu, 2 Jun 2005, Marco Baringer wrote:

> "Hamilton Link" <helink at sandia.gov> writes:
>
>> I'd be a little surprised if this could be made to work without major
>> kludges, unless you constrain your use more fully (and possibly not
>> even then).
>
> how major? how hard would it be to copy/restore openmcl's stack? (this
> is idle curioustiy way way way beyond my current capabilities so feel
> free to ignore this request).
>

It's fairly easy (at least conceptutally) to copy a stack.  It's
harder to ensure that the copy is usable, since there are all kinds
of things that point into stacks in non-obvious ways, and I don't
think that it'd be possible to reliably update those references.