Re^3: Correct call for dll with Win32::API

If int HCE300_Read(int TrackNo, char *ReadData); is the prototype, then it uses the default calling convention. It my understanding that's __cdecl for MS compilers. Win32::API uses the __stdcall calling convention since that's what the Win32 API (kernel32.dll, etc) uses.

Argument-passing order Stack-maintenance responsibility

__stdcall Right to left Called function pops its own arguments from the stack

__cdecl Right to left Calling function pops the arguments from the stack

	Argument-passing order	Stack-maintenance responsibility
__stdcall	Right to left	Called function pops its own arguments from the stack
__cdecl	Right to left	Calling function pops the arguments from the stack

Win32::API expects the DLL function to reset the stack, but the DLL function expects its caller to reset the stack.

Comment on Re^3: Correct call for dll with Win32::API Select or Download Code

Replies are listed 'Best First'.
Re^4: Correct call for dll with Win32::API by walto (Pilgrim) on Dec 04, 2008 at 20:38 UTC
Thanks for your help and patience with my lack of C, but does this mean I can not use Win32::API?	[reply]
Re^5: Correct call for dll with Win32::API by BrowserUk (Patriarch) on Dec 04, 2008 at 20:53 UTC
Do you have `dumpbin.exe` on your system? If so, could you post the output from the command: `dumpbin /exports HCE300_API.DLL` [download] Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply] [d/l] [select]
Re^6: Correct call for dll with Win32::API by walto (Pilgrim) on Dec 05, 2008 at 05:40 UTC
I installed Visual c++ and started dumpbin as you suggested. This is the output: Dump of file c:\Programme\HCE300B_APP\ApiLib\HCE300_API.dll File Type: DLL Section contains the following exports for HCE300_API.dll 00000000 characteristics 0 time date stamp Thu Jan 01 01:00:00 1970 0.00 version 1 ordinal base 14 number of functions 14 number of names ordinal hint RVA name 5 0 0005A51C HCE300_Break 13 1 0005B148 HCE300_Close 3 2 0005A514 HCE300_GetDeviceType 9 3 0005AFD8 HCE300_GetLastStatus 1 4 0005B2C8 HCE300_GetRecordFormat 2 5 0005B260 HCE300_GetTrack2Density 14 6 0005A52C HCE300_Open 11 7 0005A854 HCE300_Read 12 8 0005B174 HCE300_Reset 4 9 0005A4F0 HCE300_SetDeviceType 7 A 0005B268 HCE300_SetRecordFormat 6 B 0005A4D0 HCE300_SetShowDialog 8 C 0005B200 HCE300_SetTrack2Density 10 D 0005AC5C HCE300_Write Summary 1000 .edata 3000 .idata 6000 .reloc 1A000 .rsrc 2000 BSS 5B000 CODE 2000 DATA [download] I also found some more C sample code: `char ReadBuf[250]; /* Open Success */ if(HCE300_Read(2, ReadBuf) == HCE300_OK) { } else { }` [download] (I removed the unreadable chinese comments from the sample)	[reply] [d/l] [select]
Re^7: Correct call for dll with Win32::API by BrowserUk (Patriarch) on Dec 05, 2008 at 13:48 UTC
Re^8: Correct call for dll with Win32::API by ikegami (Patriarch) on Dec 05, 2008 at 14:00 UTC
Some notes below your chosen depth have not been shown here
Re^8: Correct call for dll with Win32::API by walto (Pilgrim) on Dec 06, 2008 at 07:01 UTC
Re^5: Correct call for dll with Win32::API by ikegami (Patriarch) on Dec 04, 2008 at 20:57 UTC
If there's a difference in calling conventions, yes. Unresolvable protocol differences. It could be a number of other things too. You have the wrong prototype. You are using the library in a manner it doesn't expect. There's a bug in the library. etc.	[reply]