cdecl

问题 There are (among others) two types of calling conventions - stdcall and cdecl . I have few questions on them: When a cdecl function is called, how does a caller know if it should free up the stack ? At the call site, does the caller know if the function being called is a cdecl or a stdcall function ? How does it work ? How does the caller know if it should free up the stack or not ? Or is it the linkers responsibility ? If a function which is declared as stdcall calls a function(which has a

问题 I have heard of some methods, but none of them have stuck. Personally I try to avoid complex types in C and try to break them into component typedef. I\'m now faced with maintaining some legacy code from a so called \'three star programmer\', and I\'m having a hard time reading some of the ***code[][]. How do you read complex C declarations? 回答1: This article explains a relatively simple 7 rules which will let you read any C declaration, if you find yourself wanting or needing to do so

问题 I am working on a rather large codebase in which C++ functionality is P/Invoked from C#. There are many calls in our codebase such as... C++: extern \"C\" int __stdcall InvokedFunction(int); With a corresponding C#: [DllImport(\"CPlusPlus.dll\", ExactSpelling = true, SetLastError = true, CallingConvention = CallingConvention.Cdecl)] private static extern int InvokedFunction(IntPtr intArg); I have scoured the net (insofar as I am capable) for the reasoning as to why this apparent mismatch