My recommendation (somewhat done in fltk 2.0) is that fltk NEVER throws
exceptions, and NEVER catches them.
However it is allowed that callbacks throw exceptions. These should work
and should cleanly return to the user code that catches the exception,
and it can re-run fltk without a crash. For instance if you should be
able to write:
main() {
for (;;) {
try {
fltk::run();
exit(0);
} catch (...) {
// exceptions thrown by callbacks are here!
// however fltk::run() can be called right afterwards
}
}
}
This would be a lot better than Qt.
I believe on modern machines it is pretty much impossible to link with a
lot of useful libraries unless you enable exceptions in the compiler.
This means you are paying for whatever the overhead is, whether you
handle them or not.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
