It will be possible to add multi-segment support to OrbForms (it is extremely difficult to add to PocketC). This may be in the next major version. We will add a note about the limitation to the description page. Thanks!

Excatly how significant is this limitation? I keep reading about it in the PocketC forums. Does the 65k refer to the size of the generated prc, or the amount of memory the program consumes while it's running? What happens if this limit is exceeded?

Each app has an internal "instruction code" resource which is currently limited to 65k. This is primarily due the fact that every PalmOS resource is limited to 65k in size. If you run out of instruction code space, you won't be able to make your app any larger. At that point, it's extremely difficult to further improve/update the app. What Orbforms and PocketC need is the ability to create multi-segment applications, which basically have multiple "instruction code" resources, rather than just one.

A number of PocketC users have written apps which have hit this limit (at least 5 I'm aware of). Pretty much your only options at that point are: 1) develop your own native library to off-load as much of your code as you can, or 2) switch to another development platform.

How can we see the size of this code resource? For instance, RsrcEdit shows there are a bunch of PCpc resources, and a few code resources that seem too small to be the program in a PocketC prc. Are each of the code resources limited to 64K, and is only one of these my actual program? By using resource forms rather than dynamic ones, am I moving code to a different category that allows my whole program to be larger?