DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending] Link: http://www.fltk.org/str.php?L2355 Version: 1.3.0 Fix Version: Will Not Fix Glad to see this one open again. +1 for applying the patch, or something like it that prints an error. Some folks who are making critical GUI apps will likely complain about an exit() being in the library (we've had this at least once before). A possible alternative to just an errmsg + exit() would be if FLTK had a "fatal error callback", so that mission critical apps could at least get a callback when FLTK wants to shutdown, so that the app can cleanup things that exit() can't (e.g. removal of temp files, cleanly shutting down connections to SQL servers or remote services, etc. Though I suppose an app's class dtors could handle this, as exit() does call all dtors IIRC.. only _exit() does not) Link: http://www.fltk.org/str.php?L2355 Version: 1.3.0 Fix Version: Will Not Fix _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
