Re: call_stack

From: Date: Wed, 27 Nov 2002 20:13:02 +0000
Subject: Re: call_stack
References: 1 2 3 4 5 6 7  Groups: php.dev 
Request: Send a blank email to php-dev+get-91826@lists.php.net to get a copy of this message
Hmmm.... any hints on how to get the variable name out of the stack? The code in debug_backtrace seems to only extract the value. George Andi Gutmans wrote:
I'd probably go for class::function($arg1, $arg2). Also take into consideration that the args aren't always available. Andi At 02:58 PM 11/27/2002 -0500, George Schlossnagle wrote:
Is there a concensus on how arguments should be printed out? I'm shooting right now for a 'cluck' style backtrave class::function() called at file:line Perhaps class::function() called at file:line Arguments: print_r(args) ?? Andi Gutmans wrote:
That'd be cool. At 01:32 PM 11/27/2002 -0500, George Schlossnagle wrote:
I'll do it, if you want. Andi Gutmans wrote:
At 07:23 PM 11/27/2002 +0100, Derick Rethans wrote:
On Wed, 27 Nov 2002, Andi Gutmans wrote:
At 03:41 PM 11/27/2002 +0100, Derick Rethans wrote:
On Wed, 27 Nov 2002, Miham KEREKES wrote: debug_backtrace() will be available in PHP 4.3.0 and higher.
if someone has time to implement debug_print_backtrace() that
would be
cool. Using the raw debug_backtrace() is a bitch.
If you're trying to volunteer me it's not going to work :P
Damn! Maybe someone else? :) Andi


« previous php.dev (#91826) next »