Conversation

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

Classic example of using setjmp/longjmp for error handling:

https://github.com/pnggroup/libpng/blob/0b0876829d77db0827a8cc2c4326f63be22b2aa1/manuals/libpng-manual.txt#L407