Although you can't create a PalmOS code resource larger than 64k, you might be able to create a code plugin larger than 64k. One method might be to create a big MacOS 68k code resource using the large code model. Then chop that code into data chunks smaller than 64k. On the Palm side you could then have a loader catenate these data chucks into memory allocated as a Feature Pointer (which I think allows contiguous chunks larger than 64k). Some options might be to compress the data chunks, and leaving the Feature memory around between invocations if the frequency of use of the code plugin was high enough.
The method of having one code resource load and lock down another code resource also works if you don't mind building a dispatch routine for all entry points in the 2nd code resource which you want called from the 1st. I had to do that on an Pilot application I wrote in '96, and it was a nuisance partitioning the code. For ARM code plugins, I may have to try method one above to avoid the partitioning problem, assuming the tools allow it. Ron Nicholson HotPaw <http://www.hotpaw.com/rhn/hotpaw > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
