CodeWarrior generated exception tables must fit in under 32K? Is this assertion true?
After reading much of Ben's material and after looking at my CodeWarrior link maps, I've come to understand that the exception tables must live in the addressable range (32K) beneath the A5 register. Also living beneath the A5 register is __segtable__, which takes up about 8K in my 450K app. This leaves me with about 24K for my exception tables. Is it feasible to use this "zero-overhead" implementation of exceptions with a large (400K+) project? In Ben's PalmSource PowePoint (available at www.palmoswerks.com) he mentions an expected 15:1 ratio from code size to exception table data. I assume this is when efficiently using exception specifications on methods. If my code is 450K, this would yield 30K of table data, and given the __segtable__, this probably won't fit beneath the A5 register. Has anyone done much better than 15:1? Please don't recommend that I just make my app smaller. Reuse that comes from OO and good design is much more important to my companies needs. We are using POL, MSL, and our own library that provides column-based table views and querries on PDBs. Anyone think I can get exceptions to work for this beefy piece of OO on the Palm OS? Thanks in advance for any suggestions. -Aaron -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
