On Tue, Aug 9, 2011 at 10:50 AM, Michael Sweet <m...@easysw.com> wrote: > On Aug 9, 2011, at 1:26 AM, Evan Laforge wrote: > > ... > > So it's not really about trying to clean up mistakes after the fact. > There's just not much a library can do if you passed an index out of > bounds, but it's nicer to print a trace and quit rather than segfault. > > This amounts to the same thing - an uncaught exception will cause a crash, > in many cases without any visible logging. > Again, I'm -1 on using exceptions in FLTK.
In my experience what you said isn't true. On my system (g++ and OS X), an uncaught exception means a nice error message and an exit, in all cases. But as I mentioned, I have no problem with not using exceptions since a simple log and exit callback can serve the same purpose almost as well. _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
