Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am writing a managed wrapper for a 3rd party API and I have access to only their header files and .lib file. In one of the header files there is a function:
extern "C" void functionName(unsigned int param);
To wrap this function, I can ignore the extern keyword right? It is just to tell the compiler to treat the declaration as if it were made in C, rather than C++ and I guess this shouldn’t be an issue when writing a managed wrapper using C++/CLI?
Using
extern "C"in a function declaration specifies C linkage for the function (i.e. no name mangling); see here: In C++ source, what is the effect of extern "C"? . It should not adversely affect a C++/CLI caller.