Re: Minimal pragma Export (StdCall... example?

[happysegfault@yahoo.com (Happy Segfault)]

Dmitry A. Kazakov <mailbox@dmitry-kazakov.de> wrote in message news:<2de350pqsadlrvvgkrpc7261k31l5ejuap@4ax.com>...
> 
> The pragma Export gives you an opportunity to explicitly specify the
> name used in the DLL. So you can name your Pop_A_Window as
> "pop_a_window@0". You can also move it to Visual Basic side, where you
> can explicitly specify the link name:
> 
> Declare Function Pop_A_Window Lib "my_Ada.dll" Alias "_pop_a_window"
> (...) As Long
> 
> Probably you want to automate it and omit specifying any link name
> altogether. I doubt it that is possible.
> 
> Though you can always buy GNAT Pro and try to convince ACT (GNAT
> vendor) to implement
> 
> pragma Export/Import (VisualBasic, ...);

I took a look at glBegin() as an example Stdcall function.  It appears in 
Windows' OPENGL32.DLL as glBegin, not _glBegin or _glBegin@4, according to 
objdump -p.  It is pramga-Import'ed in win32-gl.ads in my GNAT distribution 
with the command pragma Import (Stdcall, glBegin, "glBegin");  If I take a 
look at the symbol table for the GNAT-supplied import library libopengl32.a, 
using objdump -t, I find it listed as _glBegin@4 and not also as glBegin 
or glBegin@4.  

If I could replicate this with my own combination of a pragma Export (Stdcall, 
... and the right gnatmake, gnatdll (or directly gnatlink, gnatbind, dlltool) 
options, I think I'd have it.  Unfortunately, I've got pop_a_window@0 in my 
DLL (bad) and _pop_a_window@0 in my import library (good) at this point, 
which messes up the import into Visual Basic.  If I leave off the @0 in the 
def file, I can get pop_a_window in the DLL (good) but then have 
_pop_a_window in the import library (bad).  

Any ideas, anyone?  

Thanks for the reply!  After checking out your homepage, I'm pretty sure 
you're ten times the programmer I am!  

John