"Win32" tells the compiler that this function is using the Standard Calling Convention.
Basically this means that the parameterstack are to be cleaned by the called application/function(the dll in this case).
Read this...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/html/_core___stdcall.asp
If you remove "Win32", you will tell the compiler to use the C, C++ calling Convention.
Using this calling convention, the application calling the function is responsible for cleaning the stack(Bmax).
Now if you call the function using the C/C++ convention but the dll is using the Standard Convention I suppose both Bmax and the dll will try to clean the stack.
You can see most of the time what kind of convention a dll is using by checking the decoration of the exported functions.
They often start with an underscore(_) and end with a @ followed by the size of the parameters.
Basically this means that the parameterstack are to be cleaned by the called application/function(the dll in this case).
Read this...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/html/_core___stdcall.asp
If you remove "Win32", you will tell the compiler to use the C, C++ calling Convention.
Using this calling convention, the application calling the function is responsible for cleaning the stack(Bmax).
Now if you call the function using the C/C++ convention but the dll is using the Standard Convention I suppose both Bmax and the dll will try to clean the stack.
You can see most of the time what kind of convention a dll is using by checking the decoration of the exported functions.
They often start with an underscore(_) and end with a @ followed by the size of the parameters.