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 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($wotsit, __FILE__); >>> >>> ...but only if you specify it. I wondered since unless given a value >>> $label does nothing as to whether it could default to something like >>> __FILE__ just to make Zend_Debug a little less typing and a little >>> more useful than the PHP variations. >> >> Won't work. __FILE__ in that case would refer to the class file in >> which >> Zend_Debug lives, and it's incredibly difficult, if not impossible, to >> determine where the method was called from and what file contained >> that >> code. > > Agh of course, excuse my idiocy! > > Nick > > > > > -- View this message in context: http://www.nabble.com/Idea%3A-Zend_Debug%3A%3Adump-%24label-default-to-__FILE__-tf3912376s16154.html#a11159043 Sent from the Zend Framework mailing list archive at Nabble.com.
