Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Ivan Leo Puoti
>Hence my confusion and my call for help. The solution that comes in mind is write a test program and find out. Ivan.

Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Francois Gouget
On Sun, 22 Aug 2004, Ivan Leo Puoti wrote: > > So who's right? The platform SDK that says this is a cdecl function or > > Wine's headers? > If the SDK is wrong and is diffrent from the windows implementation, then > programs calling that function will have > problems bacause of imcompatible header

Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Ivan Leo Puoti
> So who's right? The platform SDK that says this is a cdecl function or > Wine's headers? If the SDK is wrong and is diffrent from the windows implementation, then programs calling that function will have problems bacause of imcompatible headers between the ones used to build windows and the SDK o

Re: Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Francois Gouget
Still looking in undocshell.h, I see we have: BOOL WINAPI GetFileNameFromBrowse( HWND hwndOwner, LPSTR lpstrFile, DWORD nMaxFile, LPCSTR lpstrInitialDir, LPCSTR lpstrDefExt, LPCSTR lpstrFilter, LPCSTR lpstrTitle); But in the Platform SDK's

Wrong call convention for SHAllocShared & co?

2004-08-21 Thread Francois Gouget
In the platform SDK's shlobj.h I find: HANDLE _SHAllocShared(LPCVOID pvData, DWORD dwSize, DWORD dwDestinationProcessId); Notice the lack of a WINAPI and the leading underscore. So this would indicate a cdecl API. But in dlls/shell32/undocshell.h I see: HANDLE WINAPI SHAllocShared(LPVOID pv, U