this post was submitted on 21 Feb 2025
901 points (95.7% liked)

Programmer Humor

20735 readers
368 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] codexarcanum@lemmy.dbzer0.com 6 points 1 day ago (1 children)

Wildly, in C# you can do either and it has different results. I believe a bare throw doesn't append to the stack trace, it keeps the original trace intact, while throw e updates the stack trace (stored on the exception object) with the catch and rethrow.

In C#, you can only throw objects whose class derives from Exception.

[โ€“] Hoimo@ani.social 1 points 1 day ago

You can do either, but you usually do neither. The best way is to throw a new exception for your situation and add the caught exception as an inner exception. Because rethrowing resets the stack trace, removing the context from an exception message that is often pretty vague, and "bouncing" with throw; doesn't tell the next exception handler that you already handled (part of) the exception.