Hacker News Reader

Don't use setjmp/longjmp unless you can guarantee that you own all frames between one and the other (i.e. don't use it as a public error reporting API in a library, for example). They don't play well with C++, and really anything else that needs to unwind the stack. Those who write R extensions in C++ know how messy it can be.

The only widely accepted one in that list is return codes.

> a seasoned C dev. To list a few: return codes, errno and longjump

A seasoned dev that thinks errno and longjump are good idea's should have retired 25 years ago.

Yeah, I just tried to be on the more "permissive" side of things. Though per-library errno is being used (zeromq, libuv).