🚀 go-pugleaf

From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley)
>In article <19920811.003756.988@almaden.ibm.com> peterf@vnet.ibm.com writes:
>>Firstly, under 2.0 the message parameter (msg) to your client window
>>procedure should be a ULONG, not a USHORT.
>>
>Really?  I found a prototype, in one of the headers, for window procs
>that confirmed (if you can call it that) that the msg parameter is still 
>an USHORT -- at least in whatever beta version of OS/2 that gcc took its 
>headers from.  I guess, since gcc was built on a beta release, that I 
>shouldn't take it for granted that its headers are correct.
>
>I wonder how we (the set of all OS/2 gcc users) might get a more up to 
>date set of header files, short of buying C/Set 2?  (If we had, wanted 
>or could afford C Set/2, we wouldn't be using gcc, would we?.  I know I 
>personally can't justify the price of C Set/2 for use on my home system!  
>Perhaps IBM could take a hint from that other company and offer a $69 C 
>Set/2.)  
>
>So, anyone know if a new version of gcc, based on non-beta OS/2 is 
>forthcoming from anywhere?

Take the route I did: buy the OS/2 programmer's toolkit ($79 from
Programmer's Paradise) which includes full headers for all the API's,
the library that contains link definitions for same, and a *really*
good online reference to each function, data type (structs, typedefs,
etc), and message.  

There is a conversion process needed for the header files, but I've
already done this and will be making the diffs available (on hobbes) 
so others can apply them to their copy of the toolkit headers.  (I
just have to figure out how to do it :-)

Pete