Closed bb-avn closed 9 years ago
We include the Aerospike client libraries in a C++ project. In order to avoid linker errors, every file that includes an #include directive for an Aerospike header needs to wrap those in an extern "C" block like this:
#include
extern "C"
// Aerospike -- WARNING - extern "C" required! extern "C" { #include <aerospike/aerospike.h> #include <aerospike/aerospike_key.h> #include <aerospike/aerospike_query.h> #include <aerospike/aerospike_lmap.h> #include <aerospike/aerospike_index.h> }
Could the Aerospike client library header files be made C++-safe by including this in the headers themselves?
This will be added in the next C client release.
Aerospike C client 3.1.0 has been released.
We include the Aerospike client libraries in a C++ project. In order to avoid linker errors, every file that includes an
#include
directive for an Aerospike header needs to wrap those in anextern "C"
block like this:Could the Aerospike client library header files be made C++-safe by including this in the headers themselves?