There is an ErrTry, ErrThrow, and ErrCatch mechanism for Palm. See the Palm OS API Reference manual for specifics. They work similarly to the C++ mechanism, but don't introduce the overhead.
I find exception handling useful for detecting non-recoverable problems such as device full, write out of bounds, invalid database record, etc. For other types of errors, I find the old C style error codes adequate. Some philosphers, however, will say I shouldn't mix my error handling paradigm. :-) --Mike Y. www.ytechnology.com "Matthew Henry" <[EMAIL PROTECTED]> wrote in message news:112532@palm-dev-forum... > > Maks Pyatkovskiy wrote... > > >I think it's better for all don't use C++ exceptions in large C++ apps > for Palm OS at all. The size of 1st code segment and the limit of data > segment (it can be overfull by exception info blocks) are quite serious > obstacles for C++ apps. You can avoid these problems if you'll not make > new obstacles for your own programs... > > Interesting. Anyone else care to weigh in with an opinion? > > I have a large application with "half-hearted" exception handling. > I have been toying for a long time with either making it robust with serious > exception handling (adding a lot more catches-throws, and Palm OS wrapper > functions that throw and such). Or else just removing all the exception > handling and doing it all c-style (return codes, bleh) because it's a pain > on the other launch codes, possibly more memory-intensive and bigger > executable. > I've been coding in C++ forever, so obviously I'd prefer extensive exception > handling. > But perhaps on the Palm it's just not worth it? > > Matthew Henry > > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
