sed comments on Use of setjmp()/longjmp() in code is typically a sign of laziness - and translates to "We didn't bother writing proper error handling"

Use of setjmp()/longjmp() in code is typically a sign of laziness - and translates to "We didn't bother writing proper error handling" (infosec.exchange)

submitted 1 week ago by harrysintonen@infosec.exchange to c/programming@fedia.io

3 comments fedilink hide all child comments

Use of setjmp()/longjmp() in code is typically a sign of laziness - and translates to "We didn't bother writing proper error handling". It's like using abort() but even worse. longjmp() out of the blue breaks the control flow of the application and easily leads to all kinds of resource leaks and state inconsistencies. The legitimate use cases for setjmp()/longjmp() are few and far between.#C #programming

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

[–] sed@hostux.social 1 point 1 week ago

@harrysintonen funny, to me it translates to "here is another way to deal with error handling"it's close to your translation, there is less negativity thoughespecially useful with recursive functions/data structures

permalink

fedilink

source