At 01:49 PM 12/13/2000, Lee, Eric wrote:
>I got the same error and this is how I got around it
>
>--changed the code model to Large from Small (Smart didn't do it for me)
>(32bit baby!)
Smart should work just fine. Note that every 32 bit call requires a messy and space
consuming bit of glue since the 68000 instruction set doesn't have a suitable
instruction.
>--Use 4 byte integer instead of 2 bytes
This shouldn't have anything to do with the issue. If you use integer types like Int32
and UInt16, why do you care whether int is 16 or 32 bits?
>--Multisegment.
This can help because any calls from one segment to another are exempt from the 32K
limit. Once you've gone through the trouble of breaking your application up into
multiple segments, it's often possible to return to the small memory model. This will
result in a slightly smaller and faster application with no cost to you. If your
segments are all under 32K, the small code model will always work. Bigger than that,
and you may need to arrange the files within the segment in order to work with the
small code model. When you get up near the 64K limit for a segment, it can be pretty
tricky to arrange things to work with the small code model.
--
Peter Epstein
Palm Inc. Developer
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
