On 09.08.2011, at 19:56, Michael Sweet wrote: > On Aug 9, 2011, at 1:39 AM, Ben Stott wrote: >> ... >> (depending on how things go), if the RAII graphics lock (fltk::GSave, >> currently) is unable to save the graphics state through the inability to >> acquire or init. resources, an exception could be thrown to inform the user >> that anything that happens from that point in the code is going to hell in a >> handbasket. > > How does throwing an exception help here - more than likely the app will not > be written to catch the exception (you'd need to wrap all drawing in a > try/catch block) and in the end you'll just end up with a crashed app and > lost data. OTOH, overflowing a matrix stack will just result in some strange > drawing, which is visible to the user and developer but allows the user a > chance to save their data.
I have no intention of keeping the exception "throw" in the code. I used it to get a nice debugger trace in case I have a typo in the dependency graph, not knowing that the Makefile build would barf. All exception handling ha been removed, and I will not add any new throws, tries or catches for the described reasons. Users of FLTK can still use exceptions at their hearts content of course. - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
