The current description for XDebug’s eval command is (emphasis mine)
Evaluate a given string within the current execution context. A property element MAY be returned as a child element of the response, but the IDE MUST NOT expect one. The string being evaluated may be an expression or a code segment to be executed. Languages, such as Python, which have separate statements for these, will need to handle both appropriately.
There’s no real reason to have this restriction, and I think we should allow evaluation at any stack depth, defaulting to the current frame. I propose a new optional parameter `-d` to specify the stack depth, defaulting to 0.
Max Sherman
Received on Fri Aug 26 2016 - 19:18:02 BST
This archive was generated by hypermail 2.2.0 : Sun Jun 24 2018 - 04:00:04 BST