Brilliant exception handling I found in an app i had to work on
this post was submitted on 17 Jun 2023
144 points (96.8% liked)
Programmer Humor
32174 readers
951 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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;, notthrow 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?
An exception will bubble up the stack until it enters a
catchblock that can handle it, and you may need additional logic to decide if you are finished, or it needs to go further up. (you may also intercept it just to add more data, or log it)throw;allows you send the original exception further up, butthrow ex;behaves the same as throwing a new Exception object, and therefore has a new trace. The throw statement doesn’t query any properties on the exception argument AFAIK, so it has no idea this exception has been previously thrown, but the IDE is smart enough to know you almost certainly don’t want to do this.