Re: [PHP] interesting behavior of ob_end_flush() in __destruct()

Chris Dowell wrote: I haven't searched through the archives to refresh my memory, but it's something to bear in mind. I wonder whether error messages are also not passed to the browser. I have pointed out some more aspects of this issue: Error messages and normal output are passed to the browser

Re: [PHP] interesting behavior of ob_end_flush() in __destruct()

it seems that php first ends output buffering and then calls then destructs the objects. so the output buffering is still ended when the destructor is calles. one has to unset the object to reverse that order manually. aRZed If I remember correctly, there were a number of posts about this subj

[PHP] interesting behavior of ob_end_flush() in __destruct()

I discovered an interesting behavior, when ob_end_flush() or ob_end_clean() is used in a destructor of an object. I don't think it is actually a bug, so i decided to post it here. $f = new foo(); // end of file ?> this ends in an error: Notice: ob_end_flush(): failed to delete buffer. No buffer