code organization fusturation!!!!!

ok....example....I have two .cpp files each with their own header file....they each require a definition (for multitexturing). If i define the variable in both headers, the .cpp files whine and complain that it was defined in the other file...if i but the definition in the .cpp itself, I get a million linker errors say that it was already defined in all the other .cpp files !? :confused:

I can't figure this out...my code is a bit sloppy, and not particularly well written...could that be the problem?

-psychopath

Code:

---

// put me in the shared .h file
extern int foo;

---

Code:

---

// put me in ONE of the .cpp files
int foo = 0;

---

now...you say "put me in the shared .h file"....but i said each .cpp has there OWN header....will this make a diference?

-psychopath

In one of the .cpp files put:

int myexternvar;

In the other .cpp file (and any other ones you create), put

extern int myexternvar;

You could also put the extern declarations in the header files instead of the .cpp files if you wanted to.

When you put the extern keyword in a variable declaration, it means that you are not actually declaring the variable. What is says to the compiler is that this variable is declared somewhere else, but I can use it here.

> "put me in the shared .h file".
Like common.h

Code:

---

// I'm common.h
extern int foo;

---

Code:

---

// I'm foo.cpp
#include "foo.h"
#include "common.h"
int foo = 0;

---

Code:

---

// I'm bar.cpp
#include "bar.h"
#include "common.h"

---

Of course, you could put
extern int foo;
into foo.h, and do this

Code:

---

// I'm bar.cpp
#include "foo.h"
#include "bar.h"
#include "common.h"

---

Hurray! I got it to work! (i guess fresh air helps somewhat :p)...anyway...thanks all!

-psychopath