> One of the things I noticed was that it was particularly hard with the
current documentation to determine how something was done
> before the OS 3.5 API, so I've had to assume that except in a very few
number of cases, there were no analogies and you did
> everything by accessing the hardware. So in that case, MOST of the OS 3.5
api is not backwards compatible with older OSes and it's
> just a handful of specific instructions that are.
This was one call which existed in the previous API but got renamed in the
current one, but without major changes to the functionality. Palm
eliminated the "Scr" calls and put then into their expanded "Win" API. The
trap number is the same among them both.
There have been several cases where an undocumented API that existed in
older OS versions gets promoted to documented status.
> Is my assessment of the documentation correct, or are there more OS 3.5
functions with analogous OS 3.1 calls that I'm not aware
> of? My assumption was that the easiest way to tell this was to look in
PalmCompatibility.h for possibly (but not guaranteed)
> aliased functions.
PalmCompatibility.h never had any function declarations -- it is only data
types.
--
Ben Combee
Veriprise Wireless <http://www.veriprise.com>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
