Thread: #define from a separate file

#define the macro in a separate file, and #include that file.

In practice, such a file is often referred to as a header file and given an extension that indicates it is a header (e.g. ".h").

The only thing to remember is to either ensure that no .c file #include's the file more than once (as redefining macros is not allowed). If that is not possible (eg headers that #include headers, which can occur in larger projects) look up the topic of "include guards".

I'm not sure what you mean by "I want some of the variables to do dynamic" though.

So you have in a header file (say foo.h)

Code:

#define MAGIC 1234

Then in your C file(s), you simply have

Code:

#include "foo.h"

And then later on, say

Code:

while ( var != MAGIC )

Or do you have something else in mind when you say "something" (It's rather vague)

Well if you're hoping to get from say

Code:

#define func(a,b)  a+b

to

Code:

#define func(a,b) a*b

without any recompiling, then you're going to have to do a LOT more work than using the pre-processor.

Even simple constants would need to be stored and parsed from a text file at run time (not #include at compile time).

Eg.
[config]
MAGIC = 1234
You open the file, you read the lines and you parse out the words and values.

But you still have to compile the program for every OS anyway.
But if you're referring to being able to change some settings without compiling the executable, then you would need a configuration file somewhere. Defines won't do this. You need to store information in a file and read that file.