Kall

First I tried exporting like this:

But the actual name exported was not foo but something like _foo@43253.

Then I tried this:

And the exported name became similar to _foo@8.

Is there any way that the exported name of the function is just foo?

Thanks for your time.

Sebastiani

__declspec (dllexport) should only be defined when compiling the dll. You could do something like this:

And then:

Kall

Thank you very much for the info!

Doing it that way makes it more maintainable, but the results are the same. I keep getting a dll with that function exported but with the name of "_foo@4" instead of "foo".

I generated that dll with the actual foo function, just as you wrote it.

Thanks for everything and your time,
Kall.

matsp

Yes, the naming convention of the function is based on the calling convention. Since DLL's are (normally) called by STDCALL calling convention, it appends a @X where X is the number of bytes cleaned up by the calling function. This avoids problems where the caller passes N parameters, and the function cleans up the space of M parameters and M != N.

In the CDECL calling convention, it's the caller cleaning up the stack, so the compiler in itself is responsible for both putting the arguments ON the stack and taking them OFF the stack when the function has returned. This means that there is no need to keep track of the number of bytes passed to the function in itself in the same way (e.g. passing an extra argument won't cause the stack to go out of whack).

Why do you care what the function name is? I'm sure you have good reasons, I'm asking to understand what the right solution may be, not because I don't think you have a good reason.

Edit: I should point out that WINAPI will become stdcall calling convention once the compiler sees the code.

--
Mats

__________________
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.

Kall

Don't worry for asking . I'm trying to write a plugin for a closed source program (so I can't access its sources). The program looks for a certain function in plugins DLLs in runtime which represents an interface with it, that's why the exported name needs to be exactly the same what they say. That function returns a pointer to a structure composed by some flags and several defined functions so that it can interact with the plugin.

In the SDK there is an example of how that function is (or may be) and they use WINAPI as calling convention.

Thanks for everything and your time,
Kall.

CornedBee

You can use linker definition scripts (.def) to export functions with unmangled names.

__________________
All the buzzt!
CornedBee

"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law

Kall

Thanks! I'll try that and see if it works.

If it is because of the calling conventions, can I remove WINAPI safely as it becomes stdcall in the end? I've noticed that removing it the name of the functions is the correct name, but I wonder if the program could load it correctly.

Thanks for everything,
Kall.