Make debug_zval_dump and var_dump prints int and float the same

[laruence]

debug_zval_dump prints int as long, float as double

however var_dump prints int as int, float as float

this PR make them output the same (var_dump's behavior)

[laruence]

@weltling RM, what do you think of this? could this be merged to master(7.0)?

thanks

[weltling]

One real usage i could find on github is https://github.com/symfony/symfony/blob/2aeaa22e3171b5e1f10f2cc2a7ff7f6608b65f9d/src/Symfony/Component/VarDumper/Cloner/VarCloner.php#L293 ... this change doesn't break it. Otherwise don't see any PHP project making real use of debug_zval_dump(). However you know, it's only github.

What is more concerning, IMHO, things like https://github.com/hippyvm/hippyvm/blob/c8a1d94b59d71af89133e099bfcbb43cea54a6a4/test_phpt/ext/standard/array/extract_variation1.phpt or HHVM which might have not enough time to catch up when we do it just momentary, keyword "language specification".

@laruence did you do some research about the projects impact, too?

Thanks.

[laruence]

@weltling as I can see, it's not common used, only debuging purpose.. anyway, this is just for consistency, and doesn't improve anything. so..... accepting or not accepting are both fine ;)

[weltling]

@laruence yeah, debug is obviously not an issue, i thought more to check whether it'd break some unit test or code. But don't see it currently.

I would suggest wait a couple of days for some more feedback, and then take it in? Then we'll see during next week whether something is possibly wrong and can revert it? I'm sure i can rely on your experience in this regard. Consistency is good, on the other hand - it's not a critical issue.

Thanks.

[laruence]

@weltling okey, no problem, thanks :)