Hi Scott - thanks for your reply, "Scott Johnson" <[EMAIL PROTECTED]> wrote in message news:77153@palm-dev-forum...
> > From: Igor Siemienowicz [mailto:[EMAIL PROTECTED]] > > 2. Do the Palm SDK macros unwind the stack properly for C++ objects > > (calling destructors, etc)? > No. C++ exceptions and Palm OS exceptions are not related. That's what I thought - the PalmOS exceptions seem to be a 'setjmp/longjmp'-type solution; these have driven me crazy in the past, back before exceptions were widely implemented in C++ compilers. Since my original post, I did a few cursory experiments with mobileStudio and SDK 3.5 (I know it's not the latest by a long shot, but it's the one that mobileStudio is set up for). Anyway, standard C++ try/throw/catch code DID compile OK (no errors or warnings), but when I tried to run it on POSE, I got a stack overflow when executing the 'throw' statement. Has anyone got any experience with this? Would SDK 4.0 fix the problem? > > perhaps someone could point me to the correct resource? > It's a reasonable question but the latest SDK docs don't seem to explicitly > answer it. I'm sure David Fedor can get that fixed. I did check those docos, and it would be great to have this question answered authoritatively. I'm happy to work without exceptions if they're going to be too much hassle (or bloat my code too much), but I do quite like them for error handling. Igor Siemienowicz -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
