Home/ Questions/Q 6638051
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T23:23:20+00:00

Consider the following header file example: shared_example.h #ifndef SHARED_EX #define SHARED_EX const int Shared_Int

  • 0

Consider the following header file example: shared_example.h

#ifndef SHARED_EX
#define SHARED_EX

const int    Shared_Int     = 1;
const char * Shared_CString = "This is a string";

#endif

The shared_example.h file is included in multiple compilation units, which leads the linker to (correctly) complain that:

error LNK2005: "char const * const Shared_CString" (?Shared_CString@@3PBDB) already defined in First_Compilation_Unit.obj

Removing the Shared_CString constant from this file eliminates the issue.

So, I have two questions.

First, why doesn’t the Shared_Int constant trigger the same issue?

Second, what is the appropriate way to allow separate compilation units to make use of the same constant string value?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The first declaration is of a constant integral value. In C++, const has internal linkage by default.

    The second declaration is of a pointer to const char. That declaration is not const itself, and has no other linkage specifiers, so it does not have internal linkage. If you changed the declaration to const char * const it would then become a const pointer to const char and have internal linkage.

    • 0