Bug #17612 Updated: print_r, var_dump - disable direct output

ID: 17612 Updated by: postings.php.net@hans-spath.de -Summary: print_r, var_dump, var_export - disable direct output Reported By: postings.php.net@hans-spath.de -Status: Closed +Status: Open Bug Type: Feature/Change Request Operating System: All PHP Version: 4.2.1 New Comment: Ok, but what about print_r and var_dump? I don't like to have three functions doing a similar job but expecting different parameters. Furthermore the documentation for var_export should be more clearly. IMO "You can also return the variable representation by using TRUE as second parameter to this function." says it returns just the content of the variable as var_dump($var,true) did some time ago (IIRC). Previous Comments: ------------------------------------------------------------------------ [2002-06-05 08:49:24] derick@php.net The second parameter to var_export makes the function return the information into a string, so this functionality is already implemented in someway. (also, IMO having it as an option is not an option :) Derick ------------------------------------------------------------------------ [2002-06-05 08:46:34] postings.php.net@hans-spath.de print_r, var_dump and var_export generate direct output. I don't like that, because when I dump a variable that contains HTML tags it messes up my output. I don't like to use some ob_* functions to get that output into a string before I can pass it through htmlentities because that's inperformant and looks ugly. I would like to have a function or a ini setting that controls the behavior of print_r, var_dump and var_export. There should be two modes: direct output and returning a string. I think that would be great to people who want to write debug informations into an external file, too. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17612&edit=1