Programmer Humor

32600 readers

76 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

[email protected]

144

Brilliant exception handling I found in an app i had to work on (media.kbin.social)

submitted 1 year ago by [email protected] to c/[email protected]

31 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] Pieisawesome 1 points 1 year ago (1 children)

Throwing exceptions are very costly due to the stack trace, so building the stack trace twice will cause a big performance hit

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Correct me if I'm wrong, but this will actually cut the stack trace and then start another one from your try-catch block, which is an evil thing to do towards those who will actually read your stack traces. To preserve the stack trace you do throw;, not throw ex;, and I'm assuming IDE is underlining that statement exactly for this reason.

[–] Pieisawesome 1 points 1 year ago

Yes, hence why I mentioned it collects the stack trace twice.

It's more than just more difficult for debugging