The basic data types used by the Palm OS Cobalt APIs are different from those declared in the 68K-based SDKs. In Palm OS Cobalt a signed 16-bit integer is declared as an int16_t
, whereas in a Palm OS Garnet application you would have declared it as Int16
.
Be aware that the Palm OS Protein C/C++ Compiler treats the char
type as unsigned. Code compiled using a compiler that treats the char
type as signed may need to be modified in order to function correctly.
NOTE: Early in the porting process you may want to
#include PalmTypesCompatibility.h
(after the #include
for PalmOS.h
). This header file defines a number of APIs and macros that allow applications using Palm OS Garnet data types to compile and run. This compatibility header should not be counted on long-term, however, so later in the porting process you should remove the #include
and fix any problems that result.
Unlike with the 68K-based versions of Palm OS, Palm OS Cobalt does not use traps to handle calls to operating system functions.
Deleted APIs
Nothing. Palm OS Cobalt functions aren't accessed via a trap. |
|
Nothing. Palm OS Cobalt functions aren't accessed via a trap. |
Table 80.3 Deleted enumerated types
Modified APIs
Unchanged APIs
Table 80.6 Unchanged structures
Char1 |
|
WChar2 |
1. The Palm OS Protein C/C++ Compiler treats the
char type as unsigned. Code compiled using a compiler that treats the char type as signed may need to be modified in order to function correctly.
2. Although still declared in the Palm OS Protein headers, the
WChar type is deprecated. Use wchar32_t , or wchar16_t if you need an explicit 16-bit value for UTF-16/UCS-2 Unicode support. |
Table 80.9 Unchanged application-defined functions