Re: Refcount in var_dump()

Ya, I guess this could be confusing to most users. I don't think this should be a debug only item because this could be used to help an extension developer get useful debug info from a bug reporter, and I can see no possible harm in having an extra function. How about dump_internals() ? I was thinking I could create an internal helper function called php_dump_internals(), that could also be called at the debugger. dump_internals() could possibly have verbosity and depth options. What do you guys think? -Jason On Thu, 2002-02-07 at 01:47, Yasuo Ohgaki wrote: > Markus Fischer wrote: > > On Thu, Feb 07, 2002 at 07:17:52AM +0100, derick@php.net wrote : > > > >>On Thu, 7 Feb 2002, Markus Fischer wrote: > >> > >> > >>>>me. I think it would really confuse people. I suggest adding another > >>>>function. It should probably be only enabled in debug builds because the > >>>>end user shouldn't be worrying about refcounts. It's an internal > >>>>thing. > >>>> > >>> Certain function only available in a debug build!? Please > >>> don't ... > >>> > >>having var_dump_with_refcount on a production box makes no sense at all. > >>(IE. You will never debug extensions on a production box). I'm for a new > >>function which is disable in non debug builds. > >> > > > > Achja ? I don't think sometimes you suddenly just 'right now' > > find a new bug in a code running on a production side. And > > right now the dev-box isn't properly configured to test > > exactly this environment. What now ? > > > > IMHO it's a disaster to enable/disable function dependent on > > --enable-debug or not. Does it hurt if it's always available? > > Not really. > > > > > > How about create a new module? > > -- > Yasuo Ohgaki > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > -- Jason T. Greene Internet Software Engineer <jason@inetgurus.net> <jason@php.net> <jason.greene@tdstelecom.com> Use PHP: http://www.php.net