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. ________________________________________ Michael Sweet, Easy Software Products
_______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
