Simply put, if your app must work on both 3.1 and 3.5, then use only 3.1
calls. The SDK docs clearly state which calls are OS/3.5 only.
Alternatively, grab the PalmOS version # (or the appropriate features) and
code around the version. But really, there's only a few things 3.5 can do
that 3.1 can't do, so I'd try to stick with 3.1 ...
PalmCompatibility.h is basically just there to convert types, etc. for you.
I'd develop with the 3.5 SDK. There are a few instances where you'll need to
use a function that has a 3.1 and a 3.5 version, but only a few.
"DIAMOND JEFF" <[EMAIL PROTECTED]> wrote in message
news:40633@palm-dev-forum...
>
> I'm trying to write code that works under both OS 3.5 and OS 3.1.
>
> The only way to insert OS 3.1 specific calls into my OS 3.5 compiler SDK
> is to include <PalmCompatibility.h>.
>
> But what this header does is simply rephrase my OS 3.1 call back to its
> OS 3.5 analogy.
>
> Now my question is this:
>
> If this compile method would actually work on a 3.1 device, then I
> should also be able to just use the OS 3.5 call to begin with, and it
> will magically call the old routines under OS 3.1. So there is really
> no need to use the 3.1 calls if they have a 3.5 analogy.
>
> But if it doesn't work this way, and <PalmCompatibility.h> is solely to
> allow OS3.1 calls to run under OS 3.5 (but does not truly support OS3.1
> calls) then what technique is needed to create an OS 3.1/OS3.5 hybrid
> PRC?
>
> Thanks for the information!
> - Jeff
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
