On Mon, 15 Nov 2004, Landon Bradshaw wrote:
> An example of what I was trying:
> (cmd) eval -i 16 -- print $array[0]
> <response command="eval" transaction_id="16"><property address="1242724"
> type="string"
> encoding="base64"><![CDATA[print+array0]]></property></response>
If you use "base64" as encoding, you need to encode the data as base64,
and nor urlencoded.
> (cmd) eval -i 16 -- print($array[0])
> <response command="eval" transaction_id="16" status="break"
> reason="ok"><error code="205"></error></response>
>
> The error code "205" was what I was going to report ... according to the
> docs this code is related to breakpoints while error code "206" is
> related to eval ...
That was a typo in the code, which I just fixed in CVS. (CVS version
also shows the error messages in clear text since a week).
> We're trying to understand how the eval command works so we can
> implement it properly ... any examples you might have lying around?
It would do the same as normal "eval" would do in PHP; no extra example
I have though.
But please, use the bugsystem for bugs, and the mailinglist for
questions.
regards,
Derick
-- Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.orgReceived on Mon Nov 15 2004 - 18:55:05 GMT
This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST