Description:
------------
It appears that bug #26814 caused a minor change in how include, include_once, require, and require_once function.

In spirit of how include works versus require, I would like to see execution continue on include and include_once E_PARSE errors.

It makes sense for require and require_once to stop script execution, since failure causes a fatal error, while include and include_once only issue a warning.

If nothing happens with this, the documentation needs to be changed. "Be warned that parse error in required file doesn't cause processing halting." is still present.

It would help a lot if include reflects the documented behavior once again.

Jeff Kent

Reproduce code:
---------------
(file 1) test.php
<?php
  @include "no_exist.php";
  echo "Test1\n";
  @include "e_parse.php";
  echo "Test2\n";
?>

(file 2) e_parse.php
<?php
  echo "Parse error\n
?>


Expected result:
----------------
Test1
Test2


Actual result:
--------------
Test1