Re: vxdcall calling convention

[Alexandre Julliard]

Patrik Stridvall  writes:
> However, I don't think it is enough. It will work for the
> implemented VxDCall that pops the stack itself, however it will not
> work for unimplemented VxDCalls since they will not clean up the
> stack correctly AFAICS.

The problem is you don't know how many args to pop. In theory the name
of the function tells you that, but in practice apps don't call the
right version, and VxDCall pops the number of args the specific call
requires no matter which version of the function is called. So this is
how we do it too.