🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

> "Muzzy" <leyandrew@yahoo.com> wrote in message
> news:3ff276c0$1@newsgroups.borland.com...
> 
> 
>>typedef bool (*HVPNSTART)(void);
> 
> 
> You are missing the calling convention.  That line should be more like the
> following instead:
> 
>     typedef bool __stdcall (*HVPNSTART)(void);
> 
> 
>>Everything works perfect until... i add an argument to
>>the DLL fucn VPNStart:
> 
> 
> You did not show that actual declaration.  Perhaps you copy/pasted the other
> declaration by accident?
> 
> 
>>typedef bool (*HVPNSTART)(ShortString);
> 
> 
> Again, you are missing the calling convention, it should be this instead:
> 
>     typedef bool __stdcall (*HVPNSTART)(ShortString);
> 
> 
>>It starts to act WEIRD!!!
> 
> 
> As well it should.  By neglecting to include the appropriate calling
> convention in your typedef, you are corrupting the stack when you actuall
> call the exported function.  In the absence of any explically specified
> calling convention, the compiler uses the default convention of __cdecl.
> However, the actual DLL function is using __stdcall instead of __cdecl.  The
> two conventions manage the stack very differently in regards to who (the
> caller or the callee) pushes and pops the function parameters on the stack,
> in what order the parameters are pushed, etc.  Since you are mixing
> conventions, the exported function is being called differently than the DLL
> actually expects, and as such your application goes crazy.
> 
> 
Yeap, thank you Remy! I already added _stdcall and it works fine now.