hello, i think that the fault exists in your script.
if you copied these lines directly, then your missing a right bracket

if(!@include("file_with_parse_error.php"){

should be

if(!@include("file_with_parse_error.php")){

i just spotted this and didn't run the script as i'm having a problem with windoze..

sorry if this is wasting your time :)

Description:
------------
I just upgraded to the latest snapshot and now find that Parse Errors
stop the excecution of the script with an error. 
So now i have the choice between displaying no error as to whats
happened and a blank page coming up, or displaying an ugly php error
telling the user things about my files, because i cannot catch parse
errors with php's error handling functions.

Reproduce code:
---------------
if(!@include("file_with_parse_error.php")){
    die("There has been a problem generating this page");
}

Expected result:
----------------
If the file had a parse error or didnt exist, it would die with that
error. Or even better i could have it email me.

Actual result:
--------------
Now it just prints "Parse error: parse error, unexpected ..." even
though i have put the @ symbol before it. It also gets through output
buffering.

hello, i just ran the script and i get this message - 

"There has been a problem generating this page"

so... maybe you should check your ini settings..

If the file doesnt exist, then it will work as expected, but if the file has a parse error then it will halt the script on my PC.

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php