Bug #17612 Updated: print_r, var_dump, var_export - disable direct output
| From: | derick@php.net | Date: | Wed, 05 Jun 2002 12:49:25 +0000 |
| Subject: | Bug #17612 Updated: print_r, var_dump, var_export - disable direct output | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-9542@lists.php.net to get a copy of this message | ||
ID: 17612
Updated by: derick@php.net
Reported By: postings.php.net@hans-spath.de
-Status: Open
+Status: Closed
Bug Type: Feature/Change Request
Operating System: All
PHP Version: 4.2.1
New Comment:
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
Previous Comments:
------------------------------------------------------------------------
[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