David Sparrman wrote in a message to Daniel Morgan:

 DS> Here i have to insert a question about the 'C' way of doing things.
 DS> LIB-files, how do the work? I compile my programs for MSGAPI32.DLL
 DS> anno '94 , but Scott changed the MSGAPI32.DLL before Max 3 was
 DS> released - will my programs work even if they are compiled for the
 DS> 'old' msgapi, with an old .LIB file? 
Yes they will work with older libraries.  It is called backwards compatibility.

 DS> Obviously not. I think Windows would be a little bit confused if it
 DS> was asked to do a DosDevIOCtl call, just as OS/2 would be confused
 DS> by a DeviceMode call :) 
This DosDevIOCtl()?  Is this the OS/2 equivalent of malloc()?  How does
memory work in OS/2.  I have heard of LDTs and the GDT.  How does one go
about
assigning memory and then freeing it.

DM> Good Luck!  The headers for Squish are complex.  It is best to 
DM> learn C 
DM> again to use the msgapi.

 DS> Ok, i will give it a shot. If i get to frustrated perhaps my C++
 DS> package gets itself a shot from something with a heavy caliber 

 DS> But this far everything have worked out well.

DM> /*  These are function pointers to memory functions you care to use
DM>  *  within msgapi, if the function pointer is NULL, then the msgapi will
DM>  *  use its own internal memory functions. 
DM>  */

DM>   minf.palloc      = 0x0L;
DM>   minf.pfree       = 0x0L;
DM>   minf.repalloc    = 0x0L;
DM>   minf.farpalloc   = 0x0L;
DM>   minf.farpfree    = 0x0L;
DM>   minf.farrepalloc = 0x0L;

 DS> Really nice to see! The documentation really got me comfused on
 DS> this point with those 'pointer-functions' with lots of bizarre
 DS> parameters. Just 0x0L... I like that!
It took me awhile to figure it out.  I kept on getting strange results
because I didn't assign the function pointers to anything.  

 - Daniel Morgan 
--- timEd/2 1.10