*), and the dynamic stack can have other things on it like
prompts, I thought it best to give it a new name.
I see your point about the old name, but I find the new name
confusing. What about the stack that holds regular program variables
and temporaries? That is also dynamic, so at first I
Hi!
Andy Wingo wi...@pobox.com skribis:
On Tue 06 Mar 2012 18:20, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com skribis:
I have pushed a patch to master that changes the implementation of the
dynamic stack
The “dynwind stack” actually (I misread it the first time
Hi,
Andy Wingo wi...@pobox.com skribis:
I have pushed a patch to master that changes the implementation of the
dynamic stack
The “dynwind stack” actually (I misread it the first time.)
from being a linked list on the heap to being an actual stack. This
allows us to push items on the stack
Greets :)
On Tue 06 Mar 2012 18:20, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com skribis:
I have pushed a patch to master that changes the implementation of the
dynamic stack
The “dynwind stack” actually (I misread it the first time.)
Yes, it did have this name before
Hello,
The “dynwind stack” actually (I misread it the first time.)
Yes, it did have this name before. (More often, the wind list.) But
since dynwind is overloaded so much (dynamic-wind operator, dynwind,
scm_dynwind_*), and the dynamic stack can have other things on it like
prompts, I
Hi,
I have pushed a patch to master that changes the implementation of the
dynamic stack from being a linked list on the heap to being an actual
stack. This allows us to push items on the stack in many cases without
allocating memory at all.
This has become particularly important in `master
