A small correction:
$backTrace = debug_backtrace();
$label = $backTrace[ 0 ][ 'file' ] . ' ( ' . $backTrace[ 0 ]['line'] . '
)';
HTH
On 6/18/07, Shekar C Reddy <[EMAIL PROTECTED]> wrote:
$backTrace = debug_backtrace();
$label = $backTrace[ 1 ][ 'file' ] . ' ( ' . $backTrace[ 1 ]['l
$backTrace = debug_backtrace();
$label = $backTrace[ 1 ][ 'file' ] . ' ( ' . $backTrace[ 1 ]['line'] . '
)';
HTH
On 6/12/07, Matthew Weier O'Phinney <[EMAIL PROTECTED]> wrote:
-- Nick Lo <[EMAIL PROTECTED]> wrote
(on Wednesday, 13 June 2007, 01:28 PM +1000):
> One of the pains of using
Hi,
On 6/17/07, oetting <[EMAIL PROTECTED]> wrote:
I think it is a good idea though. It would be possible to achieve this by
popping somthing out of debug_backtrace() within the dump function.
Or maybe it would be even better to implement a logger in the first case. ;-)
It's a painful lesso
I think it is a good idea though. It would be possible to achieve this by
popping somthing out of debug_backtrace() within the dump function.
Jacob
Nick Lo-2 wrote:
>
> On 13/06/2007, at 1:43 PM, Matthew Weier O'Phinney wrote:
>
>> -- Nick Lo <[EMAIL PROTECTED]> wrote
>> (on Wednesday, 13 Ju
On 13/06/2007, at 1:43 PM, Matthew Weier O'Phinney wrote:
-- Nick Lo <[EMAIL PROTECTED]> wrote
(on Wednesday, 13 June 2007, 01:28 PM +1000):
One of the pains of using print_r() or var_dump() is the hunt to find
the ones you forget to remove or edit out. With Zend_Debug::dump()
the additional $l
-- Nick Lo <[EMAIL PROTECTED]> wrote
(on Wednesday, 13 June 2007, 01:28 PM +1000):
> One of the pains of using print_r() or var_dump() is the hunt to find
> the ones you forget to remove or edit out. With Zend_Debug::dump()
> the additional $label parameter allows you to go...
>
> Zend_Debug($
One of the pains of using print_r() or var_dump() is the hunt to find
the ones you forget to remove or edit out. With Zend_Debug::dump()
the additional $label parameter allows you to go...
Zend_Debug($wotsit, __FILE__);
...but only if you specify it. I wondered since unless given a value
$
