I'm interested in hearing from anyone that has created large C or C++ Palm OS applications using the 68K back-end. I'm using PODS Version 1.2.1.02 anyone with PRC-Tools 68K experience should be applicable as well.
I'm successfully using a number of code segments to get around the 32K coderes limitation. My concern now is with the 32K datares limit. Is it true that the compiler/linker uses globals to maintain the jumps between segments? I've reached a point in the app where I can add a few functions to a class which then results in the datares full .bss error. If I remove those functions, then the error goes away. Does anyone understand how much data the global jump table consumes for each function? Is there anything I can do to avoid this? I'm already using the -fno-exceptions -fno-rtti I still have a fair amount of code to write, and have become very concerned that I'm hitting a wall. I'm in the process of changing the few global variables I have to be dynamic via MemPtrNew. But, if each class/function creates global data, then I need to re-think my design since I'll just run out at some point anyway. How about Contstants. Do they contribute to the datares size? Since I hope to move the app to other devices some day, I thought that using c++ along with isolating the OS API calls inside of classes was the smart route vs sprinkling OS specific calls throughout the application. Now I'm beginning to wonder if this is reasonable given the limits of the 68K processor/compiler. I appreciate this is not a very precise question. Thanks in advance for any insight you can share. Thanks! -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
