>So, we're fixing this by creating a new type that accurately >represents a >memory manager handle, and can pretty much only be used with >the Mem* or >Dm* routines. That lets people clean up a lot of dangerous >code, because Please, please tell me that this will not break any existing code. I'm really tired of "cleaning up" all my sources everytime I install a new version of the PalmOS SDK. Please don't take source code compatibility between API versions lightly. If parameters change, create new API function names and mark the existing ones as deprecated in the docs. Thanks, Andreas
- Re: 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.
