Programmer Humor @lemmy.ml Zadyra @kbin.social 1y ago

Brilliant exception handling I found in an app i had to work on

13 comments

Seen this so many times, i weep for humanity
“I’ll come back to this”
I'm offended that you'd put my code on the internet.
Actually, exception rethrowing is a real thing - at least in Java. You may not always want to handle the exception at the absolute lowest level, so sometimes you will instead "bubble" the exception up the callstack. This in turn can help with centralizing exception handling, separation of concerns, and making your application more modular.

It seems counter-intuitive but it's actually legit, again at least in Java. lol
- Rethrowing caught exception in C# is just throw;, not throw ex;. This will delete old stack trace, which is very punishable if someone debugs your code later and you're still around.
  
  I am a somewhat new C# developer (2 years). Could you explain more about this?
- If your just going to let something higher on the call stack handle it, why catch it in the first place?
This can't compile, can it? Only a madman commits code which doesn't compile.
Lol what’s wrong with this if the parent function catches it
- If this is C# (and it looks like it is), this leads to you losing the original stack trace up until this point.
  
  The correct way to do this in C# is to just throw; after you're done with whatever you wanted to do in the catch.
  
  wait what ?
  
  So you are saying that the following code will keep throwing e but if I used throw e; it would basically be the same except for the stack trace that would be missing the important root cause ?!
  
  try { } catch (WhateverException e) { // stuff, or nothing, or whatever throw; }

13 comments