Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64042
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
Sender: mike.php.net@gmail.com
In-Reply-To: <50B1F9D7.80000@php.net>
References: <50B1F9D7.80000@php.net>
Date: Mon, 26 Nov 2012 10:19:20 +0100
Message-ID: <CALJZF3hNQWxaXh5Gn0HgO=9LFJxxE_2Wx_bW3MYGvBC4u=GxHg@mail.gmail.com>
To: Casper Langemeijer <langemeijer@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: Bug 61272
From: mike@php.net (Michael Wallner)

On 25 November 2012 11:58, Casper Langemeijer <langemeijer@php.net> wrote:
> Hi all,
>
> Somewhere in May this year I discovered that our software would not run on
> PHP 5.4 because of changed behaviour of ob_start(). I discovered a bugreport
> that was marked 'Not a bug', but valuable info was already added to it. I
> contacted Michael Wallner (mike) directly because he marked the bug 'not a
> bug'. No response.

I'm sorry that the new output control layer causes you such headaches.

IIRC, 6 years back, when I implemented the new output control functionality,
I kindly asked the list, whether to rather implement what's documented, or
what the old code did, but I have yet been unable to find according mails.

It pretty well may have been the case that the old code passed the
output buffer contents through the handler prior discarding, but as it had
not been documented (and I obviously failed to figure out a use case) I
apparently implemented the more efficient way it currently is.

No offense, no excuse, just a try to figure out what happened...

-- 
Regards,
Mike