Comments by Pesmontis (Top 4 by date)

I've got it to work with the following changes:

#define FUNCDECL(ret, name, args) \
typedef ret (__cdecl *raw_##name) args; \
raw_##name* name = (raw_##name*)&_##name;

and:

FUNCDECL(unsigned int, GetUncompressedLength, (void*, unsigned int));

So this means I had to stop using standard calls, and I think that it is necessary to specify the exact function arguments (ie. without my own parameter names). Therefor I can now answer my own first question:

It is not necessary to create class prototypes in order to address the exports listed above (even / only for member functions from singleton classes).

The answer to the second question is: you can probably use a force cast as suggested by the codeguru article if you use a __cdecl convention. However, this is not necessary therefor I have not tested it.

The answer to the third question is: if you address the function(s) properly, using proper arguments, then the return value is indeed the function result. This will be a pointer if it is specified as a pointer. In the example I described above, the output was produced with improper function arguments. I should not have added argument names.