Description:
------------
I had this problem a million times. It's very easy to accidentally invoke "Fatal Error: Call to a member function .. on a non-object". The problem is that this triggers an error so fatal that it can't even be caught by the shutdown function. This recently gave me a huge headache in a production system where an obscure bug where a variable contain null which was called on invoked a silent crash. It's a headache because I run everything in a framework with great wrappers for error handling/detection that are suppose to send me an email when obscure bugs get tripped. This obviously doesn't work when the PHP commits seppuku and explodes.

I don't see any reason for this error to be that fatal. Sure, keep the error fatal but at least allow the shutdown function to catch it.

Test script:
---------------
\register_shutdown_function(function(){
    $e = \error_get_last();
    if (!\is_null($e))
        die('Houston we have a problem: ' . \print_r($e, true));
});

$hello = null;
$hello->bar();

Expected result:
----------------
Houston we have a problem: Array
(
...

Actual result:
--------------
Fatal error: Call to a member function bar() on a non-object in ...