Re: (dll) __stdcall functions and GetProcAddress

From:

"Scot T Brennecke" <ScotB@MVPs.spamhater.org>

Newsgroups:

microsoft.public.vc.language

Date:

Thu, 7 May 2009 09:48:44 -0500

Message-ID:

<uXh4sLyzJHA.4632@TK2MSFTNGP02.phx.gbl>

Well, yes, but I thought we were talking about stdcall convention, which isn't used on x64. 64-bit
builds are always fastcall, which passes 4 parameters in the registers rcx, rdx, r8, and r9. These
days, stdcall is only really relevant on 32-bit. However, you can use the __stdcall declaration on
64-bit builds and it will be ignored, which might confuse some people.

"Alexander Grigoriev" <alegr@earthlink.net> wrote in message
news:%23YQiSnxzJHA.2480@TK2MSFTNGP06.phx.gbl...

Those names can be different in x64 build.

"Scot T Brennecke" <ScotB@MVPs.spamhater.org> wrote in message
news:eJxp2FtzJHA.5964@TK2MSFTNGP04.phx.gbl...

Alternatively, those names ARE reliable. They always begin with an underscore, and the numeric
value after the @ is the number of bytes in the parameter list:
http://msdn.microsoft.com/en-us/library/x7kb4e2f(VS.80).aspx

You can call GetProcAddress on _Add@8

"K?r?at" <kursattheking@gmail.com> wrote in message
news:%231IeTEpzJHA.5032@TK2MSFTNGP05.phx.gbl...

Hi,

I have a very simple dll that exports a simple function "int Add (int, int)". I use the
function from an executable using LoadLibrary and GetProcAddress. When calling convention is
"cdecl" so far so good but with "stdcall" GetProcAddress returns 0. When I look at the export
list I see the function exported as _Add@8. Well, how can I dynamically address stdcall
functions from .dll's without knowing those strange (and I think not reliable to depend on)
names? AFAIK, windows API functions generally use stdcall calling convention and we can address
those functions dynamically (using LoadLibrary+GetProcAddress) using their straight names, what
is the trick?

Thanks in advance.