Confirm
496
edits
Changes
8630d68 Let 'pop' specify an arbitrary completion value, not just a return value. Clarify 'forceCompletion'.
{ "to":<i>thread</i>, "type":"resume", "forceCompletion":<i>completion</i> }
where <i>completion</i> is a [[#Completion_Values|completion value]] indicating whether the frame should return a value, throw an exception, or be terminated. Execution resumes in the current frame's caller, in the manner appropriate for <i>completion</i>.
A <tt>"resume"</tt> packet may not include both a <tt>"resumeLimit"</tt> property and a <tt>"forceCompletion"</tt> property.
The client can remove frames from the stack by sending a request of the form:
{ "to":<i>frameActor</i>, "type":"pop", "valuecompletionValue":<i>valuecompletion</i> }
where <i>frameActor</i> is the actor representing the stack frame to pop, and <i>valuecompletion</i> is a grip on the [[#Completion_Values|completion value that should be returned as the value of ]] describing how the frameshould appear to have finished execution. All younger stack frames are also popped. The thread remains paused. The frame actor will reply:
{ "from":<i>frameActor</i>, "watches":[<i>watchActor</i> ...] }
