Const and macro

You're still allowed to do this, of course:

Code:

---

// x.hpp
extern const int &x;

// x.cpp
int real_x;
const int &x = real_x;

---

Quote:

---

Originally Posted by CornedBee

Instinctively, I'd say this is undefined behaviour.

Less instinctively, gcc refuses to compile it if you pass the implementation file and at least one using file at the same time and use -combine. (-combine only works for C currently.)

---

Compiled just fine using g++. Compiled foo.o, bar.o and then linked them

Of course that doesn't mean it isn't undefined.

As I said, both files at the same time and -combine:

Code:

---

gcc -o const -combine const1.c const2.c

---

You can't use gcc to compile c++ programs. I see that I did .c instead of .cpp, sorry about that.


Both gcc and g++ gave me "unrecongized option `-combine`". Changing cout to printf and compiling both as C gave me a working program.

IMO it is pretty silly to have that be undefined behavior but oh well.

Quote:

---

You can't use gcc to compile c++ programs.

---

Yes, you can. And it was me who changed the names to .c, because -combine is not implemented for C++.

I don't know what GCC version you have. Mine is 4.1.2.

3.something. Haven't had a need to update it. When I compiled the files using gcc I got syntax errors because of std::.

#macros are beautiful

Code:

---

#define IF if(
#define THEN ) {
#define ENDIF }
#define MARRY_GO_ROUND while(1) {;}

---

so sweet

Code:

---

IF 5 == 5 THEN
    MARRY_GO_ROUND
ENDIF

---

Quote:

---

Originally Posted by (::)

#macros are beautiful

Code:

---

#define IF if(
#define THEN ) {
#define ENDIF }
#define MARRY_GO_ROUND while(1) {;}

---

so sweet

Code:

---

IF 5 == 5 THEN
    MARRY_GO_ROUND
ENDIF

---

---

Ah, so that's how VB does it! LOL!

Quote:

---

Originally Posted by cpjust

Ah, so that's how VB does it! LOL!

---

hush hush hushssssss ... do not let the secret out :D lol lol lololololololololol!!!