Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3212 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 83303 invoked by uid 1007); 3 Jul 2003 17:09:58 -0000 To: internals@lists.php.net References: <1057244229.3291.250.camel@mbe> <1057248304.3291.262.camel@mbe> Message-ID: User-Agent: slrn/0.9.7.4 (Linux) Date: Thu, 3 Jul 2003 19:09:47 +0200 X-Posted-By: 217.224.220.84 Subject: Re: [PHP-DEV] Re: var_dump_html() From: muell-spam-trash-abfall@kcet.de (Frank Wiegand) Marco Tabini wrote: >> Please have a look at PEAR::PHP::Var_Dump: >> http://pear.php.net/package-info.php?pacid=103 > Thanks, Frank, I have. But do I really want to load up a PEAR class to > dump my variables to the browser? For me, the answer is no--although, > obviously, that is only my opinion. IMHO its not PHP's job to produce HTML output for debugging purposes. I'd prefer the PEAR package, because: * You have more control about the output layout (Var_Dump.php uses skins). * There are (as said) three functions in PHP that do nearly all the same. * Using the package is not more complicated than using var_dump. It's a two liner (but you can use auto_prepend_file). Using Var_Dump makes your script slower, but (high-)speed doesn't matter while debugging PHP scripts. Frank