Also, it will allow PHP applications to recover more gracefully from this sort of error.
A properly designed PHP application that already has global catch blocks and some 500 error pages will have this sort of error come under that same error handling process rather then give an ugly blank page. I think it will make PHP look more professional altogether. [Ahm: Also new here on the list :-)] A > -----Original Message----- > From: Stefan Walk [mailto:[EMAIL PROTECTED] > Sent: 31 December 2007 13:28 > > On Monday 31 December 2007 13:48:52 Antony Dovgal wrote: > > Changing PHP's behavior in a backward-incompatible way that would affect > > everyone and *forcing everyone* to use exceptions seems to be really bad > > idea, especially taking into account that your problem can be easily solved > > without it. > > What exactly is the backwards compatibility break here? Without the change, > the code simply dies ... if you don't catch the exception, the code simply > dies ... except you get a backtrace now and can handle the exception if you > want to. > > Regards, > Stefan -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
