You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many of the command definitions start with an (unless aborting? …) wrapper around their body. It would be preferable, I think, for this clause to be part of the procedure definition rather than the command definition. One could imagine a command along the lines of (:UNLESS slot contents) which pushes contents onto the command stack when slot evaluates to an affirmative.
This might be slightly off: it's often possible that the aborting? flag is set mid-procedure, which bypasses several commands / unwinds the continuation stack a fixed amount. In this sense, what we want is more like a condition handler, or a goto.
The text was updated successfully, but these errors were encountered:
Many of the command definitions start with an
(unless aborting? …)
wrapper around their body. It would be preferable, I think, for this clause to be part of the procedure definition rather than the command definition. One could imagine a command along the lines of(:UNLESS slot contents)
which pushescontents
onto the command stack whenslot
evaluates to an affirmative.This might be slightly off: it's often possible that the
aborting?
flag is set mid-procedure, which bypasses several commands / unwinds the continuation stack a fixed amount. In this sense, what we want is more like a condition handler, or a goto.The text was updated successfully, but these errors were encountered: