Hi - > The new terminate_handler seems really useful, I wonder why something > like this isn't the default behaviour.
Yeah. > I think I understand the idea behind wrapping scan () to catch the > reportable_exception. Yup. > The sqlite_checkpoint_pb looks simpler now. But I must admit I don't > fully understand if the lifetime of the object. The sqlite_ps had a > destructor that called finalize, which I assume isn't necessary? In the new case, we're calling "sqlite3_execute" directly, which does not need finalization. > The code looks good to me. Thanks! > Did you already catch (haha, pun intended) where/what caused that odd > sparc uncaught exception? Nope. :( In the cases I saw, the error occurred right during the object ctor, but was not able to trigger it by hand or get a core dump to analyze further. - FChE