"extern const int" creates linking errors that "extern int" doesn't

Hello.

2 source files main.cpp def.cpp
main.cpp:

Code:

---

#include <iostream>
using namespace std;

extern const int a;

int main()
{
    cout << a << endl;
}

---

def.cpp:

Code:

---

const int a = 4;

---

when I compile it like this:
g++ main.cpp def.cpp -c
g++ main.o def.o

I get this error:
main.o(.text+0x12b):main.cpp: undefined reference to `a'
collect2: ld returned 1 exit status

But when I remove the "const" from the extern and from the actual definition of the value, it works. Why is it so and how to avoid id?

It looks like you're doing things backwards to me:

Code:

---

// def.h:
extern const int a;

// new.cpp:
#include <iostream>
#include "def.h"

const int a = 42;

int main() {
  std::cout << "a = " << a << std::endl;
  return 0;
}

---

imho extern is for saying: "this variable is declared elsewhere. Don't worry, compiler, I'll show you the right spot when the time comes".

thus, in main.cpp i want to use a variable that is defined in another .cpp file.
I don't want to do it your way, citizen, because if I'd want to use the const int a in another file, what should I do? define it again?

Imho I should define a variable only once, but I can use it as much as possible, not vice versa.

Help me, god of C.

try put
const int a = 42;

in the def.h and remove extern declarations

Quote:

---

In C, constant values default to external linkage, so they can appear only in source files. In C++, constant values default to internal linkage, which allows them to appear in header files.

---

it would work, but it's just ignoring the problem.

Does anyone know why the "const" wants to mess with me?

Quote:

---

Originally Posted by hardi

it would work, but it's just ignoring the problem.

Does anyone know why the "const" wants to mess with me?

---

No it means to work according to C++ standard

Quote:

---

Originally Posted by vart

No it means to work according to C++ standard

---

what do you mean?

Just what I have already said

Quote:

---

In C++, constant values default to internal linkage, which allows them to appear in header files.

---

> what should I do?
Nothing. Just make sure that it's declared:

Code:

---

// def.h
#ifndef DEF_H_INCLUDED
#define DEF_H_INCLUDED
#include <iostream>
  void print();
  extern const int a;
#endif

// main.cpp
#include <iostream>
#include "def.h"

const int a = 42;

int main() {
  std::cout<<"a = " << a << " in main.\n";
  print();
}

// again.cpp
#include <iostream>
#include "def.h"

void print() {
  std::cout << "a = " << a << " in another file.\n";
}

---

You can initialize a wherever you like. It's just that other files are dependant on def.h

it will work in C not C++

Really?

Owner@pavilion ~
$ g++ new.cpp again.cpp -w -Wall -ansi -pedantic

Someone ought to have told me that I wasn't compiling C++.

Owner@pavilion ~
$ ./a
a = 42 in main.
a = 42 in another file.

I suppose I'm magical.

Quote:

---

Originally Posted by citizen

Really?

I suppose I'm magical.

---

I suppose so

ok, I don't understand it, but actually there is no need to make a def.h containing an "extern" and a .cpp to define that externed variable - I could just put the definition in the .h file, as you recommended me, vart.

> ok, I don't understand it
The whole point of the extern keyword is to extend a variable's lifespan beyond file scope. It allows global constants to exist across an entire project.

Vart's quote from the standard states that constants are linked internally in C++ by default, allowing you to initialize a constant in a header file. In the language's predecessor, C, constants weren't allowed to be initialized in header files, so extern was used. C++ supports the extern keyword because it was inherited from C. If someone can prove that a constant must or shall be linked internally, then I'll gladly shut up.