Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:22033 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37922 invoked by uid 1010); 27 Feb 2006 20:49:07 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 37906 invoked from network); 27 Feb 2006 20:49:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Feb 2006 20:49:07 -0000 X-Host-Fingerprint: 210.55.31.88 mail.album.co.nz Linux 2.5 (sometimes 2.4) (4) Received: from ([210.55.31.88:41943] helo=www.album.co.nz) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 2B/5E-25426-1C563044 for ; Mon, 27 Feb 2006 15:49:06 -0500 Received: by www.album.co.nz (Postfix, from userid 1003) id 6840553394; Tue, 28 Feb 2006 09:49:01 +1300 (NZDT) X-Spam-Checker-Version: SpamAssassin 3.1.0-gr0 (2005-09-13) on www.album.co.nz X-Spam-Level: X-Spam-Status: No, score=0.4 required=5.0 tests=AWL autolearn=ham version=3.1.0-gr0 Received: from [192.168.0.9] (222-152-167-75.jetstream.xtra.co.nz [222.152.167.75]) by www.album.co.nz (Postfix) with ESMTP id 2D50C4E21; Tue, 28 Feb 2006 09:49:00 +1300 (NZDT) Message-ID: <440365BB.802@album.co.nz> Date: Tue, 28 Feb 2006 09:48:59 +1300 Organization: Album Limited User-Agent: Mail/News 1.5 (X11/20060220) MIME-Version: 1.0 To: Michael Wallner CC: internals@lists.php.net References: <68.AB.30574.5C7E2044@pb1.pair.com> In-Reply-To: <68.AB.30574.5C7E2044@pb1.pair.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Revisiting output control code From: jasper@album.co.nz (Jasper Bryant-Greene) Michael Wallner wrote: > I'd like to suggest that we revisit the output control (output > buffering) code base. On a semi-related note, I'd like to see the docs mention that print_r and var_export (with the second parameter set to TRUE), and debug_print_backtrace, internally use the output buffering code to capture their output, meaning that using them inside an output buffering handler will always cause a fatal error. Alternatively, I'd like to see these functions *not* use the ob functions to do their work. I realise the former is probably easier though. Jasper