Hello, > Yasuo Ohgaki <yohg...@ohgaki.net> hat am 27. Juli 2014 um 10:11 geschrieben: > > Hi Timm, > > On Sun, Jun 29, 2014 at 7:40 PM, Timm Friebe <p...@thekid.de ><mailto:p...@thekid.de> > wrote: > > > a couple of weeks ago, I proposed a change to the handling of the >situation > > where methods are called on non-objects. Instead of an E_ERROR, the > >engine would > > raise an E_RECOVERABLE_ERROR, and enable framework and library authors to > >handle > > this. [...] > > I like the idea. > > Only thing that I don't like is it depends on error message to be useful > rather than error code/status. Was this discussed? Just curious.
No, this wasn't discussed so far. You're right, this could make the code inside the error handler more readable and robust. It would mean, however, changing all the other E_RECOVERABLE_ERRORs too, like argument type mismatching and certain closure and generator operations; and thus was out of scope. I remember this from a couple of years back though; but can't recall why it was never done. -Timm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
