static global

Yes. "extern int u;" in f2.c.

yes, I know. I put that there to show that you needed to declare it with an extern in the file.

A dos prompt! Ewww!
But as I said, I'm not an expert on the matter, so...
I don't know! Go bug someone else! :p

Quote:

---

Originally Posted by Elysia

What I meant is,

Code:

---

int x = 5;

---

External linkage in C. Can be accessed from multiple .c files.
In C++, however, it's internal linkage so trying to access it from another .cpp file will yield a compile error and redefining it will yield a linking error.

---

That's untrue. It works the same as in C. You have to declare it as "extern" in the other modules that reference it.

Quote:

---

Code:

---

static int x = 5;

---

Internal linkage in C. Cannot be accessed from other .c files.
I don't know what the effect is in C++, though. I don't know if it will cause external linkage in this case.

---

Have you EVER worked on code composed of more than a single source file?

YES, I have. Hundreds of times.