Wierd var_dump() output for unserialized objects

[rybakit]

Is there a reason to dump unserialized objects to such a specific format?

object(Obj)#%d (3) {
  ["a"]=>
  int(1)
  [%r"?b"?:protected"?%r]=>
  int(2)
  [%r"?c"?:("Obj":)?private"?%r]=>
  int(3)
}

To compare, here is a standard var_dump() output for the same object (https://3v4l.org/nXGBP):

object(Obj)#1 (3) { 
  ["a"]=> 
  int(1) 
  ["b":protected]=> 
  int(2) 
  ["c":"Obj":private]=> 
  int(3) 
}

[Sean-Der]

Hi @rybakit

Is this in PHP 5 (and also is the behavior different in PHP 7)?

I think this is because we use the symtable operations, instead of the properties API? This wouldn't be hard to fix

[rybakit]

Looks like this is only the case for PHP 5 (https://travis-ci.org/rybakit/travis-sandbox#L228-L235). It would be great to bring it in line with standard PHP output ;)

[Sean-Der]

Yea totally! I agree it should be fixed.

I have a little bit of time this weekend, and will try my best to get it done then! If by Monday it isn't done feel free to poke me via GitHub/email and I will work on it right away.

thanks!

[rybakit]

Great! Thank you very much for looking into it and the quick responses!

[rybakit]

Hey @Sean-Der
Have you had a chance to look into the issue yet?

[Sean-Der]

Hey @rybakit!

Sorry I got sick/burned out, so have been doing the bare minimum amount of work the past couple of days!

Sorry for the silence, this is still on my TODO list!

[rybakit]

No worries and get better!

[m6w6]

This is expected, %r encloses regexes in tests' EXPECTF sections.