Re: RFC: Catchable "call to a member function of a non-object"

From:	Marco Pivetta	Date:	Tue, 29 Apr 2014 10:50:17 +0000
Subject:	Re: RFC: Catchable "call to a member function of a non-object"
References:	1 2	Groups:	php.internals
Request:	Send a blank email to internals+get-73842@lists.php.net to get a copy of this message

On 29 April 2014 10:26, Derick Rethans <derick@php.net> wrote:

> Programming mistakes should not be hidden by error
>

Of course, but what about having a PHPUnit tests that hard-fail due to a
"PHP Fatal error:  Call to a member function foo() on a non-object in ..."?

Just being able to have a handler that catches it as an error is pretty ok,
and it surely allows me to see if there are other failures in a huge test
suite
without having to come up with some crazy code just to run the tests one by
one.

This use case already makes it worth having this improvement in my opinion.

Cheers,

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


   

Thread (11 messages)

• php@thekid.deSun, 27 Apr 2014 12:00:39 +0000
  • mails@thomasbley.deSun, 27 Apr 2014 17:10:49 +0000
    • Timm FriebeMon, 28 Apr 2014 01:04:51 +0000
  • Levi MorrisonSun, 27 Apr 2014 18:48:38 +0000
  • Johannes SchlüterMon, 28 Apr 2014 09:07:11 +0000
    • Timm FriebeMon, 28 Apr 2014 20:35:40 +0000
  • Derick RethansTue, 29 Apr 2014 08:26:34 +0000
    • mails@thomasbley.deTue, 29 Apr 2014 08:46:08 +0000
    • Marco PivettaTue, 29 Apr 2014 10:50:17 +0000
      • Sebastian BergmannTue, 29 Apr 2014 11:42:29 +0000
      • Tjerk MeestersTue, 29 Apr 2014 12:18:47 +0000