Re:Nerd Sniping: What does the code do at the end of the page?
by deekayteez on Tuesday November 24, 2009 @06:18PM
(#960166)
in .NET its illegal - "Control cannot leave the body of a finally clause"
[ Parent
| on HN ]
Re:Nerd Sniping: What does the code do at the end of the page?
by Jupe on Tuesday November 24, 2009 @06:45PM
(#960236)
It appears MS thought this through. The contrived example is but ONE way a mediocre programmer could really munge this stuff up if the language is not specific about protecting exit points from a finall{} block.
Re:Nerd Sniping: What does the code do at the end of the page?
by echaozh on Wednesday November 25, 2009 @03:02AM
(#960822)
What about throwing exceptions in the finally block? Isn't it an exit point too?
When you call non-trivial 3rd party code from your finally block, how do you ensure it doesn't throw? Or what do you do if it does? Indefinitely nested try blocks?
Re:Nerd Sniping: What does the code do at the end of the page?
by nollidge on Tuesday November 24, 2009 @07:29PM
(#960300)
Indeed. I can't think of a reason as to why any language would even allow it.
Re:Nerd Sniping: What does the code do at the end of the page?
by Jach on Tuesday November 24, 2009 @10:56PM
(#960596)
I know it's horrible in practice, and I really can't see a valid use for this particular case, but forbidding things like this (or other things like multiple inheritance) just because it can be abused has never seemed like a good idea to me.
Re:Nerd Sniping: What does the code do at the end of the page?
by nollidge on Wednesday November 25, 2009 @12:46PM
(#961511)
It's not just that it can be abused, though - every use of it is an abuse. Finally{} is not for decisions and manipulating values and program logic, it's for cleaning up resources.