I noticed this action, I'm thinking about breaking up my custom event
handler into two pieces in order to force my call to be closer to the
start of the segment. The current problem is that the key handler for
it is located a little ways into the handler itself...I had the same
exact problem with the ScanCmdScanDisable function, as well, and moving
it up higher in the calling function seemed to work (I thought it to be
one of those mojo fixes, and just let it be).
Thanks Peter!
// Rus Daniel Nesse
>-----Original Message-----
>From: Peter Epstein [mailto:[EMAIL PROTECTED]]
>Sent: Friday, May 26, 2000 9:45 AM
>To: Palm Developer Forum
>Subject: Re: 16 Bit reference out of range linker error
>
>
>At 08:33 AM 5/26/2000, Nesse, Rustin wrote:
>>... this one call gets a 16 bit reference out of range error
>every time (It NEVER did in CW 5)...
>
>This probably means that the call site is more than 32K away
>from the called routine. If you were close to the limit
>before, minor changes to the compiler or optimizer or their
>settings could put you over the top. This 32K limit is
>inherent. You can rearrange your files in the segment view,
>and you can rearrange the routines within the files. I've
>never coded for a Symbol device, but my guess is that the
>routine you're calling is in the startup code library which is
>the first file in the segment. That means moving the call site
>closer to the start of the segment may be all you need to do.
>
>You can also switch from small to smart code model in the 68K
>Processor panel. This will cause the compiler to use long
>jumps for all inter-file calls. This will increase the code
>size and reduce performance, but it should solve your problem
>(assuming the call site and routine aren't in the same file).
>Eventually, you may need to convert your application to multi-segment.
>--
>Peter Epstein
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
