Please refresh my memory.. on this...
If you have filea.c with:
and a fileb.h with :Code:#define MYVAR 91
which manifest constant takes precedence if both files have source code that use MYVAR?Code:#define MYVAR 25
For instance, In a project setting when you compile these files to produce the executable, these manifest constants are treated
like global variables. If that is how they're supposed to work , then which #define is used?
Thanks.
You have a few misconceptions, it seems:
They're not treated like global variables. The preprocessor, which handles #defines, is basically a text substitution program. Everywhere that the token MYVAR is encountered, it is replaced by the value (91 or 25). You can see the output if you use GCC by using the -E flag:Quote:
Originally Posted by kjwilliams
For MSVC++, some hints as to compiler flags may be here (can't say how close this is, since I don't use MSVC++): http://cboard.cprogramming.com/tech-...ml#post1168446.Code:$ gcc -Wall -E filea.c
<snip>
int main(void)
{
printf("MYVAR = %d\n", 91);
return 0;
}
First, you must understand what a translation unit is. Basically, when a .c file is done being preprocessed, that is the translation unit. The result of all the preprocessing, any #includes and conditional preprocessor stuff, will tell you what value gets used. If some file, filex.c, which doesn't define MYVAR, but does include fileb.h, then it uses the value in the .h file. The only problem is when a .c file both defines a constant and includes a file defining the same constant. Multiple .c files being combined, where two different values for MYVAR may come into play, happens at the linking stage. But at that point, all preprocessor stuff has been processed, so MYVAR is no more, only it's literal values exist anywhere.Quote:
Originally Posted by kjwilliams
As an example of the problem with defining and #including:
That conditional #ifdef says, if the symbol USE_FILEB is defined, then process the include, otherwise don't. Notice that, if I to process the #include, I get a "redefined" error. That is, if filea.c #includes fileb.h, then it's a problem. If not, it uses it's own.Code:$ cat fileb.h
#define MYVAR 25
$ cat filea.c
#include <stdio.h>
#ifdef USE_FILEB
# include "fileb.h"
#endif
#define MYVAR 91
int main(void)
{
printf("MYVAR = %d\n", MYVAR);
return 0;
}
$ gcc -Wall -ggdb3 -o filea filea.c
$ ./filea
MYVAR = 91
$ gcc -Wall -ggdb3 -DUSE_FILEB -o filea filea.c
filea.c:7:0: warning: "MYVAR" redefined [enabled by default]
fileb.h:1:0: note: this is the location of the previous definition
They are both used in their own files -- unless you included the header in the file, which makes them the same translation unit.
Use #undef MYVAR if you need both at some point.Quote:
Originally Posted by C99 Draft N869
I use DJGPP which uses GCC, on Windows , is the -E flag a compiler or linker flag?Quote:
They're not treated like global variables. The preprocessor, which handles #defines, is basically a text substitution program. Everywhere that the token MYVAR is encountered, it is replaced by the value (91 or 25). You can see the output if you use GCC by using the -E flag:
> I use DJGPP which uses GCC, on Windows , is the -E flag a compiler or linker flag?
Option Summary - Using the GNU Compiler Collection (GCC)
Where is -E listed here.
Why are you using a compiler that's more than 10 years out of date, and built to work on 386 systems running DOS? Pick something modern. Perhaps Code::Blocks with MinGW, or Pelles C, both of which are currently developed and have good support communities. Or, install a virtual machine running Linux and use the real GCC.Quote:
Originally Posted by kjwilliams
As for the flag, it's neither compiler nor preprocessor. GCC is a program that incorporates a preprocessor (processes all the # directives, turning a source file into a translation unit), compiler (compiles C code from a translation unit into object code) and a linker, which links several pieces of object code into the final library/executable/whatever. The -E flag is a flag to the overall GCC program, that instructs GCC to only run the preprocessing phase, and output that.
Thats all I needed to know, thanks....Quote:
Originally Posted by anduril462