dongzhao3040 2014-07-29 03:12
浏览 49
已采纳

禁用PHP错误消息

I am working on my own custom error handler function. Currently I am trying to disable error reporting so it wont display errors to public users. However it is not working.

<?php

// Disable error reporting.
ini_set( "error_reporting", 0 );

// Create an error.
echo "hi

?>

This returns this error:

Parse error: syntax error, unexpected end of file, expecting variable (T_VARIABLE) or ${ (T_DOLLAR_OPEN_CURLY_BRACES) or {$ (T_CURLY_OPEN) in C:\xampp\htdocs\websites\sicsportsagency.com\includes\test.php on line 7

What am I doing wrong?

  • 写回答

1条回答 默认 最新

  • dongxinpa3101 2014-07-29 03:24
    关注

    You can disable error reporting for syntax errors, just for any other sort of error. But there’s a catch.

    Using ini_set like you’re doing works for errors besides syntax errors because ini_set (presumably) runs before the code that has the error in it. With syntax errors in the same file, not so. PHP must parse the whole file before it can even begin to execute the first line of code. If it encounters an error in parsing, even if that error is further along in the file, it’s still parsing and not yet executing: it hasn’t had the chance to run ini_set.

    The most straightforward solution would be to edit php.ini so the appropriate setting is set before even parsing begins.

    If you can’t do that, you might have to have to put the code that has a potential syntax error in another file, and then the original file can ini_set and require the second. Since require will only parse the required file at the point of execution of the require, you can be sure that ini_set will run before any parse error in the required script can occur.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?