Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:22036 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22059 invoked by uid 1010); 28 Feb 2006 13:47:06 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 22044 invoked from network); 28 Feb 2006 13:47:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Feb 2006 13:47:05 -0000 X-Host-Fingerprint: 212.42.230.40 pima.hostsharing.net Linux 2.5 (sometimes 2.4) (4) Received: from ([212.42.230.40:44669] helo=pima.hostsharing.net) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 9D/5B-25426-85454044 for ; Tue, 28 Feb 2006 08:47:04 -0500 Received: from [192.168.178.20] (p54AD8820.dip0.t-ipconnect.de [84.173.136.32]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pima.hostsharing.net (Postfix) with ESMTP id DC614B05C268; Tue, 28 Feb 2006 14:47:12 +0100 (CET) Message-ID: <4404544D.6060000@php.net> Date: Tue, 28 Feb 2006 14:46:53 +0100 Reply-To: betz@php.net User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Jasper Bryant-Greene Cc: internals@lists.php.net References: <68.AB.30574.5C7E2044@pb1.pair.com> <440365BB.802@album.co.nz> In-Reply-To: <440365BB.802@album.co.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Revisiting output control code From: betz@php.net (Friedhelm Betz) Jasper Bryant-Greene wrote: > 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. Open a bug report at bugs.php.net "Documentation Problem"? Friedhelm