Provide a way to pass-in the name of the "input parameter" and calling file about dump_r.php HOT 6 CLOSED

i don't really want to grow the API, so maybe the easiest thing to do here it to add a global config option that disables dump_r from showing the trace info?

from dump_r.php.

Actually, yeah, that'd be ideal. Right now, we're relying on some code to search & replace the incorrect trace info with some info we sniff out ourselves (effectively, our code is doing the same thing as dump_r, but with a different blacklist of files to ignore in the stack). So, an option to turn off the built-in support for dump_r to generate this info would be more efficient.

from dump_r.php.

added. try it out.

from dump_r.php.

Only downside with this approach is that you're still reflecting on the stack backtrace to get the information that may or may not be rendered, no?

I also noticed that Core uses debug_backtrace(), without passing DEBUG_BACKTRACE_IGNORE_ARGS, so it's getting a lot more information about the stack than it needs. I believe if you omit the args, it should reduce memory usage and improve performance of what is normally a decently heavy operation.

from dump_r.php.

i've added DEBUG_BACKTRACE_IGNORE_ARGS and moved the debug_backtrace() call out of Core::dump_r() into the global dump_r() wrapper. feel free to implement your own version of the global dump_r() on top of Core::dump_r().

see b75b5e9

from dump_r.php.

Thank you!

from dump_r.php.