Confirmed users
497
edits
(→Evaluating Source-Language Expressions: Fix packet form to match other resumptions.) |
|||
| Line 668: | Line 668: | ||
To evaluate a source-language expression in a thread, the client sends a specialized <tt>resume</tt> packet of the form: | To evaluate a source-language expression in a thread, the client sends a specialized <tt>resume</tt> packet of the form: | ||
{ "to":<i>thread</i>, "type": "client-evaluate", "expression":<i>expr</i>, "frame":<i>frame</i>, "pause-for":<i>pause-types</i> } | { "to":<i>thread</i>, "type":"client-evaluate", "expression":<i>expr</i>, "frame":<i>frame</i>, "pause-for":<i>pause-types</i> } | ||
This resumes the thread just as an ordinary <tt>resume</tt> packet does, but rather than continuing execution where the pause took place, has the thread begin evaluation of the source-language expression given by <i>expr</i>, a string. The evaluation takes place in a new [[#Client_Evaluation_Frames|Client Evaluation Frame]], pushed on the stack. When evaluation of <i>expr</i> completes, the client will report a <tt>client-evaluate</tt> pause containing the expression's value. | This resumes the thread just as an ordinary <tt>resume</tt> packet does, but rather than continuing execution where the pause took place, has the thread begin evaluation of the source-language expression given by <i>expr</i>, a string. The evaluation takes place in a new [[#Client_Evaluation_Frames|Client Evaluation Frame]], pushed on the stack. When evaluation of <i>expr</i> completes, the client will report a <tt>client-evaluate</tt> pause containing the expression's value. | ||