如何判断 PHP 致命错误何时实际上是隐藏的语法错误，以及它们何时发生？

发布于 2024-09-12 17:19:58 字数 968 浏览 4 评论 0原文

考虑以下 PHP 类：

class someObject {
    public function broken(){
        return isset($this->something()) ? 'worked' : 'didnt';
    }

    public function something(){
        return true;
    }

    public function notBroken(){
        print('worked');
    }
}

假设我现在这样做：

$obj= new someObject();
$obj->broken();

考虑到您无法将函数调用传递给 isset()（它是通过引用），我希望这样因致命错误而失败： PHP Fatal error: Can't use method return value in write context 这很好，并且符合预期。

但是，假设我现在这样做：

$obj= new someObject();
$obj->notBroken();

考虑到我在此执行中的任何位置都没有遇到 broken()，并且 broken() 中出现错误> 是一个致命错误（而不是解析错误），我不希望正常输出“worked”。 错误！它仍然会生成致命错误。

问题：

除了不编写有错误的代码之外，是否还有其他不是解析错误但仍会触发运行时错误的错误？我只知道：PHP 致命错误：无法在写入上下文中使用方法返回值。有什么方法可以检测到这些错误吗？这种类型的错误有专门的名称吗？

原文

Considering the following PHP class:

class someObject {
    public function broken(){
        return isset($this->something()) ? 'worked' : 'didnt';
    }

    public function something(){
        return true;
    }

    public function notBroken(){
        print('worked');
    }
}

Let's say I now do:

$obj= new someObject();
$obj->broken();

Considering you can't pass a function call to isset(), (it's by-reference), I expect this to fail with a fatal error: PHP Fatal error: Can't use method return value in write context This is fine, and expected.

However, let's say I now do:

$obj= new someObject();
$obj->notBroken();

Considering I'm not hitting the broken() anywhere in this execution, and the error in broken() is a Fatal Error (and not a Parse error), I wouldn't expect the normal output of "worked". FALSE! It still generates the Fatal Error.

Question:

Aside from just not writing code that has errors, are there any other errors that are not Parse Errors but still trigger a runtime error? I only know about: PHP Fatal error: Can't use method return value in write context. Is there any way to detect these errors?
Is there a special name for this type of error?

分享到QQ

分享到微博