Smart code model isn't actually very smart. It results in a performance and space penalty, but it does let your app grow right up to the 64K limit of a single segment without any extra work on your part.
Changing the link order is really easy, and often works to solve your immediate problem, but as the app continues to grow, it gets harder to find a link order that works. At some point, it's worth the work to switch to multiple segments just to avoid this headache. If you have one monolithic .c file, then changing the link order is a much bigger job, as CodeWarrior doesn't support specifying the link order within a compilation unit. Breaking a .c file into pieces is a nice thing to do anyway, but it does require some C language skills that you can get by without when you've got just one big file. Jump islands just seem like too much of a hack to me, but I've seen code that uses them, and it does let you continue to use the small code model without having to break up your code into multiple files in order to let you specify the link order. -- Peter Epstein -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
