Bug->Doc #74569 [Opn]: Return in a finally clause silently ignores an exception thrown in a try clause

Edit report at https://bugs.php.net/bug.php?id=74569&edit=1 ID: 74569 Updated by: cmb@php.net Reported by: trianman at gmail dot com Summary: Return in a finally clause silently ignores an exception thrown in a try clause Status: Open -Type: Bug +Type: Documentation Problem Package: Scripting Engine problem Operating System: Any PHP Version: 7.1.4 Block user comment: N Private report: N New Comment: It seems to me this is simply a documentation issue. Previous Comments: ------------------------------------------------------------------------ [2017-05-12 18:24:10] trianman at gmail dot com 2 danack@php.net Sorry, I don't want to be mean. My English skills are not very good and it is sometimes hard to express my thoughts in a clear way. I've just realized that the finally statement is some-kind of antipattern for me. Because finally is a shortcut for catching and re-throwing an \Exception class eg. <?php try { throw new CustomException(); } catch (CustomException $ex) { handleException(); } catch (\Exception $ex) { doThingsInFinally(); throw $ex; } doThingsInFinally(); ?> Or with finally: <?php try { throw new CustomException(); } catch (CustomException $ex) { handleException(); } finally { doThingsInFinally(); } ?> Of cause if we have a return statement instead of a doTihingsInFinally() method, we will lose an exception. But we doing it in a clear way. On the other hand finally statement hides out from developer's eyes what actually is going. So for my mind a little copy-paste is a lesser evil than an unclear behavior. For all other guys the E_NOTICE will be enough. (: ------------------------------------------------------------------------ [2017-05-11 14:28:34] olavisau at gmail dot com BC is broken with any solution. The fact that javascript behaves in the same way worries me. It's probably very hard to implement. I agree with the E_NOTICE. ------------------------------------------------------------------------ [2017-05-11 14:21:03] trianman at gmail dot com > btw The behaviour in PHP is the same as that which happens in Java > This behaviour is also that used in Javascript. Sorry to hear that, but AFAIK nor Java nor JavaScript (ECMAScript) has no conventional (standartized) way to produce non critical warnings at the run time. So PHP is better in this way and why can't we employ it? > "Don't put returns in finally" I believe that the good tool must help its users not to "shoot themselves" as much as possible. So the user becomes free from a lot of "Don't do something somewhere". If you don't agree you are free to use an assembler to do anything you want and remember a lot of such restrictions. I can imagine another more expectable an clear way to handle this case. But it will break a BC so can be implemented only in a new major release of PHP. Triggering E_NOTICE is the most convenient way for now. ------------------------------------------------------------------------ [2017-05-11 13:42:04] danack@php.net This behaviour is also that used in Javascript. function foo() { try { throw 42; } finally { return "edge cases are hard"; } }; alert(foo()); ------------------------------------------------------------------------ [2017-05-11 13:30:49] danack@php.net > but it MUST NOT be silently dropped out. That's a conclusion without rigorous justification. btw The behaviour in PHP is the same as that which happens in Java: https://web.archive.org/web/20070922061412/http://weblogs.java.net/blog/staufferjames/archive/2007/06/_dont_return_in.html It'd be a lot easier to say "Don't put returns in finally blocks, yo". > The interpreter should trigger an E_NOTICE or something similar here. This would almost certainly be better done with code analysis tools, rather than giving warnings on valid (though highly surprising) code. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=74569 -- Edit this bug report at https://bugs.php.net/bug.php?id=74569&edit=1