Confirmed users
496
edits
Remote Debugging Protocol: Difference between revisions
cc0e8cf Note that environment actors' 'binding' and 'assign' requests can elicit 'threadWouldRun' errors.
(8630d68 Let 'pop' specify an arbitrary completion value, not just a return value. Clarify 'forceCompletion'.) |
(cc0e8cf Note that environment actors' 'binding' and 'assign' requests can elicit 'threadWouldRun' errors.) |
||
| Line 883: | Line 883: | ||
{ "from":<i>envActor</i>, "bindings":<i>bindings</i> } | { "from":<i>envActor</i>, "bindings":<i>bindings</i> } | ||
Note that this request elicits a <code>"threadWouldRun"</code> error reply when <i>envActor</i> refers to an object environment whose object is a proxy. | |||
To change the value of a variable bound in a particular lexical environment, the client can send a request to the environment's actor: | To change the value of a variable bound in a particular lexical environment, the client can send a request to the environment's actor: | ||
| Line 895: | Line 897: | ||
{ "from":<i>envActor</i>, "error":"immutableBinding", "message":<i>message</i> } | { "from":<i>envActor</i>, "error":"immutableBinding", "message":<i>message</i> } | ||
If <i>envActor</i> refers to an object environment whose object is a proxy, or whose property named <i>name</i> has a setter function, this request elicits a <code>"threadWouldRun"</code> error reply. | |||
== Lexical Environment Examples == | == Lexical Environment Examples == | ||