Well, this change won't break any EXECUTABLE code. The types are all the
same to the CPU.
Your sources, however, are toast. VoidHand and Handle no longer exist. In
general, you'll need to search/replace them with MemHandle.
We plan to create an OSCompatibility.h file that *will* include the old
definitions, they will either be typedef'd or #define'd to the new ones.
In fact, the file should be in the SDK, but it's pretty empty right now.
Now that (many of) you have the CD, you'll probably be wanting this soon.
...we know! If someone takes a shot at filling out the file, they might
consider sending it in to us (via DevSupp) to save some time.
--Bob
- PalmOS API change (Was: Re: VoidHand vs. Handle) Andreas Linke
- Re: PalmOS API change (Was: Re: VoidHand vs. Handl... David Fedor
- Re: PalmOS API change (Was: Re: VoidHand vs. Handl... John Marshall
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Richard Hartman
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Bob Ebert
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Linke, Andreas Dr.
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Aaron Ardiri
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Bob Ebert
- Re: PalmOS API change (Was: Re: VoidHand vs. Handl... John Marshall
- Re: PalmOS API change (Was: Re: VoidHand vs. Handl... Scott Johnson
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Linke, Andreas Dr.
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Richard Hartman
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Bob Ebert
- RE: PalmOS API change (Was: Re: VoidHand vs. Handl... Richard Hartman
