2

I created a static library on Windows using Visual Studio 2008 with these two files:

header file was a simple C API:

#ifdef __cplusplus
extern "C" {
#endif

   void init();
   void stop();

#ifdef __cplusplus
}
#endif

Implementation however was using C++ features:

#include "my_lib_api.h"

#include <iostream>

void init() {
   std::cout << "Initializing my_lib\n";
}
void stop() {
   std::cout << "stopping my_lib\n";
}

I then built with these commands:

mkdir Release
cl.exe /O2 /Oi /GL /D "WIN32" /D "NDEBUG" /D "_LIB" /FD /EHsc /MT /Gy /Fo"Release\\" /W3 /c /Zi /TP my_lib_api.cpp /nologo /errorReport:prompt
lib.exe /OUT:my_lib_api.lib /LTCG .\Release\my_lib_api.obj /NOLOGO

I then copied my_lib_api.lib and my_lib_api.h to a new folder where I created a new Visual Studio console application with a main.c source file:

#include "my_lib_api.h"

int main(int argc, char* argv[]) {
  init();

  stop();
  return 0;
}

I built using same /MT multi-threaded C runtime library to be consistent with library. It then built like this:

mkdir Release
cl.exe /O2 /Oi /GL /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /FD /EHsc /MT /Gy /Fo"Release\\" /W3 /c /Zi /TC .\main.c /nologo /errorReport:prompt

successfully created Release/main.obj

link.exe /OUT:c_api_so.exe /INCREMENTAL:NO /MANIFEST:NO /SUBSYSTEM:CONSOLE /OPT:REF /OPT:ICF /LTCG /DYNAMICBASE /NXCOMPAT /MACHINE:X86 my_lib_api.lib kernel32.lib user32.lib shell32.lib .\Release\main.obj /NOLOGO /ERRORREPORT:PROMPT

Successfully created c_api_so.exe which runs just fine.

This means I can write a library in C++ and as long as I provide a C API then both C and C++ calling programs can use my library? Is this universally true? Should this always work? Why does it work? I assume that for each platform you would say only support one compiler/linker and provide eg on Windows a Visual Studio based library and on linux a GNU C based library? Are there any issues to be aware of?

Angus Comber
  • 9,316
  • 14
  • 59
  • 107
  • 1
    _"This means I can write a library in C++ and as long as I provide a C API then both C and C++ calling programs can use my library?"_ Yes _"Is this universally true?"_ Yes _"Should this always work?"_ Yes _"Why does it work?"_ Because C++ includes all of the C language. Anyway your question is too broad as is. – πάντα ῥεῖ Aug 30 '14 at 15:58
  • As a note, use `void init(void)` etc. in the header. In C, empty parentheses mean that the compiler doesn't need to check if you call it with the correct number of arguments (and it cannot in this case). E.g. `init(5)` would compile (but may crash when run, for example). – mafso Aug 30 '14 at 16:05
  • @mafso: I don't believe that's true in Standard C. I thought they adpoted the C++ way of doing it. – Puppy Aug 30 '14 at 16:33
  • @Puppy: No, they take care not to break old code more than absolutely necessary. Empty parentheses still mean "fixed, but unspecified number of default-promoted arguments". Only implicit function declarations were dropped (in C99). – mafso Aug 30 '14 at 16:50

1 Answers1

4

Broadly speaking, a function is an interface. All the caller cares about is that it meets that interface. The implementation is totally irrelevant. In this case, by using extern "C" you told the C++ compiler to make a binary interface that the C compiler can use, which it did. The interface is a match (guaranteed by Standard), so you can quite safely call it from C. Just to re-state, the body is totally immaterial here and may be implemented in any language at all, ever. Many languages offer the power to define functions that can be called from C.

To be slightly more specific, the C ABI (ABI is the name for the binary interface here) is not specified by Standard, but virtually all operating systems have a defined C ABI that everybody on that platform uses. This is the major reason that C is still the "lingua franca" of programming- virtually everybody can speak C on a binary level.

Puppy
  • 144,682
  • 38
  • 256
  • 465