The easiest thing to do is to put the offender in a new segment,
especially if sacrificing a tiny bit of performance and a little bit
of size won't be a problem.
Less easy but better for size/performance is to go to CW's link order
tab and rearrange the files in the segment so the offender is closer
to the function/file it wants or vice versa. This can get tricky if
the segment is close the 64K limit already or any single source file
is really big. Sometimes you can even help the problem by moving the
function within its own source file.
If you change code model from 'small', set it to 'smart'. This will
let CW go to 'large' when it needs and use 'small' when it works.
Going straight to 'large' can bloat your app size.
Seperate segments work well when you can group functionality. Put
things that call each other a lot together in a segment.
Ok, getting off the soap box. Good luck
Walt
-------------------
>you can add segment in CW to avoid this problem, or you can set 68K
>process code model to smart or large if you app is not very large.
>
>
>> OK, I understand the basics of the 64 K limit (I think). But I have a
>> fairly large app, that is not even close to completion, for which I get
>> "Link Error: XForm: XFunction 16-bit code reference to YFunction is out of
>> range" a lot. I was wondering if there is some setting in CW that I can
>> make to help me out. I have a lot of features left to add, so the code is
> > going to continue to grow. Any suggestions?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
