Comment and clarify top-level evaluation & barriers

This commit is contained in:
Asumu Takikawa 2012-08-31 16:25:27 -04:00
parent ab5403d1ed
commit cd23fd48cf
2 changed files with 4 additions and 1 deletions

View File

@ -24,7 +24,8 @@ followed by @cppi{scheme_eval_compiled}.
The functions @cpp{scheme_eval}, @cpp{scheme_apply}, etc., are
@defterm{top-level evaluation functions}. Continuation invocations are
confined to jumps within a top-level evaluation.
confined to jumps within a top-level evaluation (i.e., a continuation
barrier is installed by these functions).
The functions @cppi{_scheme_eval_compiled}, @cppi{_scheme_apply},
etc. (with a leading underscore) provide the same functionality

View File

@ -5632,6 +5632,8 @@ call_with_continuation_barrier (int argc, Scheme_Object *argv[])
{
scheme_check_proc_arity("call-with-continuation-barrier", 0, 0, argc, argv);
/* scheme_apply_multi() is a top-level evaluation function and will
thus install a continuation barrier */
return scheme_apply_multi(argv[0], 0, NULL);
}