note 67909 rejected from function.ob-start by bjori

Note Submitter: guenther dot stadler at gmx dot net ---- To all those out there who like using nested ob_start()s: I just had an interesting thing of a parse-error (or a not-defined function name) not being put out to the browser... I had a snippet like that: ob_start(); include('foo.inc.php'); $content = ob_get_contents(); ob_end_clean(); And the file foo.inc.php called a function that did not exist. The problem was that PHP did not stop and give me an error message, but instead continued after the include-line. I don't know if thats a bug or a feature, but it took me almost an hour to find out that PHP had just silently skipped an error message. Greets, Günsch.