Thank you for your suggestions. This bit in your PalmSource presentation
(under 'Header Hacks to Reduce Overhead') is very intriguing, but I'm having
troubling implementing it.
The page says, "In PalmTraps.h, modify the OS_CALL macros to add "throw ()"
to the prototypes" First off, I assume 'PalmTraps.h' should be
'PalmTypes.h'? I don't see 'PalmTraps.h' anywhere in the 4.0 SDK. Assuming
that's right, I don't understand where to add the throw specifier. The
'_OS_CALL' macros have definitions like this:
#define _OS_CALL(table, vector) = { 0x4E40 + table, vector }
I tried to figure out how these macros are used, but I seldom work so close
to the API, and couldn't make much sense of it. I made a few guesses, but
ended up with syntax errors. Am I being terribly dense here? Where exactly
does the throw specifier belong?
Thanks again for the help.
"Ben Combee" <[EMAIL PROTECTED]> wrote in message
news:85109@palm-dev-forum...
>
> In article <85071@palm-dev-forum>, [EMAIL PROTECTED] says...
> > Short of removing my exception code, is there any way to compile this
app
> > without resorting to expanded mode? Is there perhaps a more efficient
way to
> > structure my exception handlers so as to shrink the exception tables? Or
> > should I just increment my SOL counter and start working on those
callback
> > thunks?
>
> Using throw specs can help some. See my paper from PalmSource 2002 for
> a simple modification you can make to the Palm OS headers that will tell
> the compiler that no OS routine throws an exception, and can reduce the
> size of your exception tables by 15-20%. See
> http://www.palmoswerks.com/stories/storyReader$44.
>
> Outside that, check my site for some more thoughts on exceptions. Use
> the "disassemble" function to try to find out where your big table hits
> are.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
