>Well, here's where the problem comes in on Mac. You can't just tell a >programmer on Mac to dispose of the pointer received. There are four kinds >of memory, and since the ANSI C runtime libraries are not part of the OS, You sure about that? My MPW programs get linked to stdclib (in the extensions folder) >but usually statically linked into the external, every XCMD has its own >version of free() and delete. It is not practiceable to have the XCMD >dispose of memory it received from the host in a cross-platform way, as the >only calls that would work this way are DisposePtr() and DisposeHandle(), >which are inherently Mac-specific. Let the caller create the memory for the >CopyXXX() calls and the problem is solved.
- Re: xTalk: Call for participation: external API extensions diskot123
- Re: xTalk: Call for participation: external API extensions M. Uli Kusterer
- Re: xTalk: Call for participation: external API extensions M. Uli Kusterer
- Re: xTalk: Call for participation: external API extensions CATkeeper
- Re: xTalk: Call for participation: external API extensions Doug Simons
- Re: xTalk: Call for participation: external API extensions M. Uli Kusterer
- Re: xTalk: Call for participation: external API extensions M. Uli Kusterer
- Re: Re: xTalk: Call for participation: external API exten... MP0werd
- Re: Re: xTalk: Call for participation: external API exten... MP0werd
- Re: xTalk: Call for participation: external API extensions Doug Simons
- Re: Re: xTalk: Call for participation: external API exten... M. Uli Kusterer
- Re: xTalk: Call for participation: external API extensions M. Uli Kusterer
- Re: xTalk: Call for participation: external API extensions Doug Simons
- Re: xTalk: Call for participation: external API extensions diskot123
- Re: xTalk: Call for participation: external API extensions Doug Simons
