On 09.08.2011, at 14:37, MacArthur, Ian (SELEX GALILEO, UK) wrote: > I still think it is possible (rushed or not) that the decision to leave out > exception handling support was a deliberate choice based on their experience > with embedded "convention" rather than simply expediency. Most of the tools > used do have exception support these days, so it is almost more work to > inhibit it than to leave it on...
I think FLTK ran fine for so many years without it. There is no reason to introduce it now. I'll remove the current code. I'll have to do error handling from scratch anyway, with or without exceptions. > > In other news: if Ben wants to do an Adroid NDK port, well, I say yes! > > Well, it'll depend on how it fits in with Matthias' plan for FLTK3. Plus, > I've got a bucketton of porting 2.0-to-3.0 to do as well as a GPA to > maintain, so it probably won't come about until ~December..... > Just enough time to get flkt3 stable then... ;-) I'll be happy to support FLTK3 on Android NDK as well as I can. It brings us to the next modernization issue though. Many of our widgets are not touch-screen friendly at all... . UI element designers! To your arms! - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
