>That's two jumps, so it's a tiny bit slower,
>but now you can reach (almost) from one end of the 64K segment to the
>other, since the jump island in the middle gives you a "stepping stone";
>each branch will be less than 32K. This will start to break down as you
>get near the 64K limit, but in my experience it works pretty well for
>apps between 32K and around 50-60K.
IMHO, modifying your application code in this way is a very short term
solution, and will ultimately fall down (as noted above). The original
poster stated they already had CW4, which solves both the 32K and 64K
problem (we've used it to solve both problems, and it really works). Why
not use it?
Personally, I'd be only too happy to move out of the IDE to makefiles and
command line builds with GCC, but limitations like the one in this thread
are just killers. Is there any move afoot to provide a smarter linker or
other tool-based solution under GCC that overcomes both the 32K jump limit
and the 64K app size limit?
Glenn Bachmann
President
Bachmann Software and Services, LLC
http://www.bachmannsoftware.com
Software Development for Handheld & Mobile Computing, Windows and the Internet
Home of Bachmann Print Manager, the only graphical printing solution for
the Palm Computing Platform