Hi,
Yes, I think that if one go for capturing the stack via copying frames then
that's the way
to go. This makes rewinding and unwinding fast. on the other hand,
currently in guile-log
we use very small linked frames so that essentially all the stored
information is lying in the
heap compressed to
On Tue 08 May 2012 21:16, Stefan Israelsson Tampe
writes:
> I have three stacks
> 1. a control stack that stores undo information scheme hooks aka
> dynamic-wind and stack references to the other stacks.
Have you seen dynstack.[ch] on master?
> 2. stack from which data is allocated from like t
hi all,
I have now implemented stack closures that can be pushed out to the heap
if we want to store a state. This is how it works.
I have three stacks
1. a control stack that stores undo information scheme hooks aka
dynamic-wind and stack references to the other stacks.
2. stack from which data
