Re: GNAT and a very foreign DLL

[Ted Dennison<dennison@telepath.com>]

In article <mailman.1010181542.30574.comp.lang.ada@ada.eu.org>, Alexandre E.
Kopilovitch says...
>  The problem appears to be with the combination of the call convention and
>the names of the DLL's entry points: the call convention is surely Stdcall,
>but the entry point names do not contain usual suffixes "@nn" - they look as
>common C identifiers.
..
>  As the Stdcall convention is unavoidable anyway, I was forced to create some
>"post-linker", which post-processes my executable, replacing "@" in the DLL's
>entry point names by zero bytes. After that post-processing all works fine,

If the problem is just the name, why don't you just use the "Link_Name"
parameter to "pragm Import" to specify the name they actually used?

However, you may want to check the C header files for that routine to make sure
the calling convention is what you think it is. I have seen DLL's with routines
with different conventions in them before.

---
T.E.D.    homepage   - http://www.telepath.com/dennison/Ted/TED.html

No trees were killed in the sending of this message. 
However a large number of electrons were terribly inconvenienced.