At the moment we need to manually check that expression is integer or not

Another one related issue - http://youtrack.jetbrains.net/issue/WI-7864

Why are you requesting it with quotes? None of the linked issues show me that Xdebug tells you there is a property key called '1'.

@derick
Ok, linked issues are not obvious.So, please look at log.

Suppose you have array which contains another arrays as its children.
$a
-1:$child1

Eval of the expression '$a' will return you the following response:
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug&quot; command="eval" transaction_id="12"><property address="12642876" type="array" children="1" numchildren="1" page="0" pagesize="100"><property name="1" address="38266496" type="array" children="1" numchildren="1"></property></property></response>

We can detect the child name only using the value of 'name' attribute.
If I will try to get children content I will append this name as array key name:
<- property_get -i 13 -n $GLOBALS['IDE_EVAL_CACHE']['dc4480db-4360-46d8-bc22-2d41f5455d7d']['1'] -d 0 -c 1 -p 0

But Xdebug will return me an error:
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug&quot; command="property_get" transaction_id="13" status="break" reason="ok"><error code="300"><message><![CDATA[can not get property]]></message></error></response>

At the moment you need to wrap name with quotes when the key name is string, and don't wrap it when the key name is integer.

Hmm, this is something we should fix in the protocol, by f.e. adding a name_type key. What do you think of that?

But why Xdebug can't treat $arr['1'] and $arr[1] in the same way? PHP actually do that.

derick, do I need to elaborate my question?

I had another good look at this, and although I understand what you're wanting I am going to have to decline it.

Running eval on a property should be avoided, I think i have mentioned this before already. Eval can return a structure, but because the result is just PHP variable content (ie, there is no associated property name), the resulting property only contains the "name" attribute. This attribute is only meant for display purposes and not for contructing further property_get commands.

If you would use a real property_get with a property name, then the resulting property structure will have for each element an extra attribute called full_name. This attribute's value is meant to be fed back to property_get and will include the full correct qualification for keys - including quotes around strings and excluding quotes around numbers.