PalmOS API keyword lists
Metrowerks Codewarrior includes a feature called Syntax Coloring
(accessible in the Preferences menu, IDE Preferences, Text Colors).
These keyword lists are provided for use in the Custom Keywords
section. They allow you to use the most recent PalmOS SDK while
developing for devices that don't run the most recent PalmOS release.
For instance, you can be warned when you use a call introduced in 3.5
when you are targeting Handspring Visors running only 3.1.
I derived these lists myself from the Palm documentation and include
files. There are probably mistakes. Use at your own risk, share
freely.
Original lists
- api30.txt. Posted on a developer forum
sometime in 1998 or 1999. Function names in PalmOS 3.0.
- 31new.txt New function names in PalmOS 3.1.
- international.txt Function names
in the International Feature Set.
- newserial.txt Function names in the
New Serial Manager.
- 32new.txt New function names in PalmOS 3.2.
- inetlib.txt Function names in the
Wireless Internet Feature Set.
- 35new.txt New function names in PalmOS 3.5.
- 40new.txt New function names in PalmOS 4.0.
- expansion.txt Function names in the
Expansion Manager.
- vfs.txt Function names in the VFS Manager.
- notification.txt Function names
in the Notification Manager.
- changed.txt Functions that have
changed parameters or functionality since PalmOS 3.0.
- gluelib.txt Functions in the Glue Library.
- hostcontrol.txt Functions and
typedefs in POSER's HostControl.h.
- system_only.txt Functions that are
marked "System Use Only" in at least one SDK (but note that some
of these are private in one SDK and public in another).
Derived lists
These are combinations of the above components. This is what I use
when developing. If I want to restrict myself to 3.5 calls, I'll load
"35yes.txt" as Custom Keyword Set 1 and make it purple, "35no.txt" as
Custom Keyword Set 2 and make it green, "hostcontrol.txt" as Custom
Keyword Set 3 and make it orange, "system_only.txt" as Custom Keyword
Set 4 and make it yellow.
A better way to do it would be to make the keyword sets vary per build
target. Set this in the Project preferences panel instead of the IDE
preferences panel. The downside of this is that you must make the
change for each build target in each project file.
These derived lists are built with derived.sh.
- PalmOS 3.0: 30yes.txt and 30no.txt
- PalmOS 3.1: 31yes.txt and 31no.txt. International Feature Set and New
Serial Manager assumed to be present from 3.1 forward.
- PalmOS 3.2: 32yes.txt and 32no.txt. INetlib assumed to be present in
3.2 only.
- PalmOS 3.5: 35yes.txt and 35no.txt. Notification Manager assumed to
be present from 3.5 forward.
- PalmOS 4.0: 40yes.txt, 40no.txt, and 40maybe.txt. 40maybe.txt is the
Expansion and VFS managers, which would be absent on upgraded devices
built before the m50x series.
Updates?
There might be an updated version. If so, it's here.
Hal
Mueller <hal@mobilegeographics.com>
http://www.mobilegeographics.com/
Last modified: Thu Sep 18 01:05:47 PDT 2003