#39389 [WFx]: of course it would be helpfull

ID: 39389 User updated by: corinl at gmx dot de -Summary: make some errors catchable Reported By: corinl at gmx dot de Status: Wont fix Bug Type: Feature/Change Request Operating System: linux debian PHP Version: 5.2.0 New Comment: well, assume you change the name of an methode. in a big project, it takes hours / days to make sure, all affected places have been adjusted. to find the missing ones you have either to get the "white page" (error page) yourself, a customer has to provide the info or you would have to look for "fatal error..." in the error logs of php. having this catchable, i could make php send me a nice email with backtrace when such an error occurs... :) also when dealing with higly dynamic objects it could be very usefull to find logic/programming errors, which only occur in a special context. without a backtrace (with the internal php fatal error unluckily does not output), it's very hard to debug such errors. Previous Comments: ------------------------------------------------------------------------ [2006-11-06 08:34:05] derick@php.net Actually, they do... and why would you want to catch that in the first place? It's a coding error which you catch while testing your code. ------------------------------------------------------------------------ [2006-11-05 16:59:00] corinl at gmx dot de Description: ------------ i assume php errors like -- Fatal error: Call to a member function ... on a non-object Fatal error: Call to undefined method ... -- don't leave php in an instable state. these errors should also be catchable by a custom error handler using E_RECOVERABLE_ERROR as it help's a lot with debugging. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=39389&edit=1