this post was submitted on 17 Jun 2023
10 points (91.7% liked)

Programmer Humor

32721 readers
347 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
cat_programmer@lemmy.ml
10
Brilliant exception handling I found in an app i had to work on (media.kbin.social)
submitted 2 years ago by Zadyra@kbin.social to c/programmerhumor@lemmy.ml
5 comments fedilink hide all child comments
 

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

top 5 comments
sorted by: hot top controversial new old
[–] ipkpjersi@lemmy.one 2 points 2 years ago (1 children)

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

[–] TwilightKiddy@programming.dev 1 points 2 years ago

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.

[–] Shareiff@lemmy.world 0 points 2 years ago (1 children)

Lol what’s wrong with this if the parent function catches it

[–] grimmi@feddit.de 1 points 2 years ago (1 children)

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.

[–] jyte@lemmy.world 1 points 2 years ago* (last edited 2 years ago)

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; 
}