Marcus Boerger wrote:
> Hello Michael,
>
> ok current name and other options in one list:
>
> 1) get_debug_info()
> 2) get_debug_hash()
> 3) get_dump_vars()
> 4) get_dump_hash()
>
> does this list contain anythign you like?
No, sorry :)
How about get_tmp_properties?
Cheers,
--
Michael
--
P
Hello Evert,
assuming you mean that as an array cast you were wrong. If you convert a
SimpleXML instance to an array you get either the current element, the
current attribute or the text or all elements or all attributes. For
ArrayObject/ArrayIterator you would get either the properties or a copy
Ignore this message if it doesn't make sense..
wouldn't this essentially be the same as __toArray() ?
Evert
Marcus Boerger wrote:
Hello Michael,
ok current name and other options in one list:
1) get_debug_info()
2) get_debug_hash()
3) get_dump_vars()
4) get_dump_hash()
does this list contai
Hello Michael,
ok current name and other options in one list:
1) get_debug_info()
2) get_debug_hash()
3) get_dump_vars()
4) get_dump_hash()
does this list contain anythign you like?
best regards
marcus
Tuesday, January 16, 2007, 8:32:41 AM, you wrote:
> Marcus Boerger wrote:
>> Hello internal
Marcus Boerger wrote:
> Hello internals,
>
> the attached patch introduces a new handler to the engine that is
> supposed to help debugging overloaded objects. It allows to return a
> temporary hash rather then the object properties. This way an extension
> can show non properties in var_dump()
the attached patch introduces a new handler to the engine that is
supposed to help debugging overloaded objects. It allows to return a
temporary hash rather then the object properties. This way an extension
can show non properties in var_dump() and print_r(). It will be used
in extensions like S
