mirror/guile
mirror/guile
1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-05-22 04:30:19 +02:00
Code Activity

Fix scm_i_vm_capture_stack comment.

Browse source 
* libguile/vm.c (scm_i_vm_capture_stack): Fix a comment.
This commit is contained in:
Andy Wingo 2014-02-19 11:19:10 +01:00
parent f2d592185f
commit ee1c6b575f
1 changed files with 3 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

14
libguile/vm.c
View file

@ -108,17 +108,9 @@ scm_i_vm_cont_print (SCM x, SCM port, scm_print_state *pstate)
scm_puts_unlocked (">", port); scm_puts_unlocked (">", port);
} }
/* In theory, a number of vm instances can be active in the call trace, and we /* Ideally we could avoid copying the C stack if the continuation root
only want to reify the continuations of those in the current continuation is inside VM code, and call/cc was invoked within that same call to
root. I don't see a nice way to do this -- ideally it would involve dynwinds, vm_run. That's currently not implemented. */
and previous values of the *the-vm* fluid within the current continuation
root. But we don't have access to continuation roots in the dynwind stack.
So, just punt for now, we just capture the continuation for the current VM.
While I'm on the topic, ideally we could avoid copying the C stack if the
continuation root is inside VM code, and call/cc was invoked within that same
call to vm_run; but that's currently not implemented.
*/
SCM SCM
scm_i_vm_capture_stack (SCM *stack_base, SCM *fp, SCM *sp, scm_t_uint32 *ra, scm_i_vm_capture_stack (SCM *stack_base, SCM *fp, SCM *sp, scm_t_uint32 *ra,
scm_t_dynstack *dynstack, scm_t_uint32 flags) scm_t_dynstack *dynstack, scm_t_uint32 flags)