Re: stdcall / cdecl -- please clarify

new topic     » goto parent     » topic index » view thread      » older message » newer message

----- Original Message ----- 
From: "Andy Serpa" <renegade at earthling.net>
> 
> Hello,
> 
> Regarding the problem with calling functions using cdecl in .dll files:
> 
> I am not a C programmer, so this is not completely clear to me.  Will 
> the corruption/errors only occur when using the Translator?  If I use 
> the interpreter with these .dll's, do I have no worries?
> 
> Can this problem be gotten around by using the Translator with Watcom 
> for my Euphoria programs, or is it the .dll that needs to be altered?  
> (I believe the latter, but I'm not positive.)
> 
> Would it be possible to make a simple "intermediate" C program or .dll 
> that is called with stdcall, which then in turn calls the desired .dll 
> using cdecl?  In other words, my Euphoria program calls a function in a 
> .dll using stdcall.  That fuction calls the 2nd .dll  using cdecl.  
> Would this slow things down?
> 
> 
> Andy Serpa
> renegade at earthling.net

This is an intersting subject and one Im struggling with aswell.
I tried to use a method presented by Matt Lewis on a cdecl .dll
and it doesnt work still if the .dll is designed for call_backs to
your program. Im guessing this might have something to do with
non-reintrant Euphoria. I just dont know.

I hope Robert clears this up in the future...

Euman
euman at bellsouth.net

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu