On Jan-29, Jonathan Sillito wrote: > 1) coroutine.t (which should be put in t/pmc/) exposes some errors in our > coroutine code. > > 2) coroutine.patch fixes those errors by saving and restoring more of the > coroutine's context. More specifically the user_stack, control_stack and > pad_stack. > > 3) document.patch (some of this this was submitted before but not applied) > adds documentation for the push_pad op to core.ops, which I somehow missed. > It also brings pdd06_pasm.pod up to date. I do not like maintaining > documentation in more than one place, so in pdd06_pasm.pod I put a terse > (but correct) description along with a reference to the generated > documentation in docs/core_ops.pod. Is that suitable???
Thanks, applied.
