Hallo Marcus,
then will you cut the protected/private functionality from print_r() (so the
engine). Probably not :) . IMO var_dump() has been always superior for usage to
print_r(). During his presentation at the last conference Derick had to change
print_r() in his example to var_dump() to show t
Hello Andrey,
if we change something then we prevent all those function from showing
private and protected values. The current situation is ok for me though.
marcus
Tuesday, May 18, 2004, 10:01:12 AM, you wrote:
> Sara Golemon wrote:
>> var_dump($someobject); shows only public properties (as I'
Sara Golemon wrote:
var_dump($someobject); shows only public properties (as I'd expect), but
print_r($someobject) shows all properties (explicitly identifying
protected/private props).
Am I wrong in thinking that's not right?
-Sara
print_r relies on a engine's routine while var_dump() does not. I h
On Mon, 17 May 2004, Sara Golemon wrote:
> var_dump($someobject); shows only public properties (as I'd expect), but
> print_r($someobject) shows all properties (explicitly identifying
> protected/private props).
>
> Am I wrong in thinking that's not right?
I think the current way is perfectly alr
