Hi internals,
what do you think about adding an optional parameter to debug_print_backtrace() (PHP 5
only) so instead of printing the stacktrace to get it as string. The information provided
by debug_print_backtrace() is more than the information provided by debug_backtrace().
So if the parameter is added the function will behave just like print_r() which has second
optional parameter.
I have made a patch which is available here :
http://hristov.com/andrey/projects/php_stuff/patches/debug_print_backtrace_as_string.diff.txt
Andrey
What else does debug_print_backtrace() include? If the info is more maybe
we should change debug_backtrace()?
In any case, in general I don't have a problem to do this. Might be nicer
if we could do it without output buffering though but I haven't looked at
the code to see how hard that would be.
Andi
At 11:56 PM 3/18/2004 +0100, Andrey Hristov wrote:
Hi internals,
what do you think about adding an optional parameter to
debug_print_backtrace() (PHP 5 only) so instead of printing the stacktrace
to get it as string. The information provided bydebug_print_backtrace()
is more than the information provided bydebug_backtrace().
So if the parameter is added the function will behave just likeprint_r()
which has second optional parameter.
I have made a patch which is available here :
http://hristov.com/andrey/projects/php_stuff/patches/debug_print_backtrace_as_string.diff.txtAndrey