Re: Using compiler error information to check undocumented prototypes and structures?

[Dmitry Timoshkov]

Qian Hong  wrote:
> Then we compile test.c on Windows using:
>
> gcc -sysroot /path/to/MicrosoftSDK/include test.c
>
> Then we will get some error message like:
>
> In file included from /path/to/windows.h:72:0,
>                  from test.c:1:
> /path/to/winuser.h:1935:26: note: previous declaration of
> ‘CreateWindowExW’ was here
>    WINUSERAPI HWND WINAPI CreateWindowExW(DWORD dwExStyle,LPCWSTR
> lpClassName,LPCWSTR lpWindowName,DWORD dwStyle,int X,int Y,int
> nWidth,int nHeight,HWND hWndParent,HMENU hMenu,HINSTANCE
> hInstance,LPVOID lpParam);
>
> Then we will know the correct prototype.

An undocumented API doesn't have a prototype in a header file, once
there's a prototype in SDK it's no longer undocumented :)