On 6/16/18, Stephan Beal <sgb...@googlemail.com> wrote: > > 3) Fossil effectively uses exit() to handle just about any type of > non-allocation error. i.e. there's little library-friendly error handling > in fossil.
Not just errors. If Fossil finds an opportunity to send a "304 Not Modified" reply, it does so and then immediately calls exit(0), without having to unwind the stack. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
