Richard Hulme wrote in a message to Mike Bilow:

 MB> You should also observe the proper case format for OS/2 API calls.  Most
 MB> of them, and all of the ones you are using here, are defined to use the
 MB> pascal calling convention (APIENTRY) which forces the names to upper case
 RH> ^^^^^^^^^^^^^^^^^^^^^^^^^

 RH> Actually, only the 16-bit API calls (VioXXXXX, MouXXXXX
 RH> etc.) are defined to use the pascal calling convention.  All
 RH> the 32-bit API calls are defined to use the syscall (or
 RH> 'system' depending on your compiler) calling convention
 RH> which is more than slightly different :-)

This issue seems to have taken on a life of its own.  The original question
was about case sensitivity in writing the API names in C source.  If the
API names are written in all caps in C source, then subtle bugs can result.

The point was that the compiler will not see the function prototypes from
OS2.H, but that the linker is going to link the functions successfully
anyway. All system APIs -- and by that I mean all of the APIs defined by
OS/2 itself, even those with "32" in their names -- are actually
exported in all caps.
 
-- Mike


---