On Aug 9, 2011, at 1:02 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote: >> Ah, thanks. I was using exception to verify my code. Now >> should I enable them for fltk3, or should I remove the >> try-catch-throw? > > I see Ben's already answered in favour of exceptions, but I have to say > that (at least for the core library) I'm not in favour. (Though, like > the STL, I have no problem with using it in user-code, of course.)
I'd have to vote -1 on exceptions. FLTK already has a mechanism for reporting exceptional conditions (Fl::fatal and friends), and the default handlers can be overridden by an app. Moreover, exceptions don't play nicely with threading and add a huge amount of overhead for simple error reporting. Better to simply make a library that doesn't crash and returns errors (when appropriate) or calls the existing exception points than to force C++ exceptions on everyone. ________________________________________ Michael Sweet, Easy Software Products _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
