#define help please

Hello,

can someone please explain to me exactly how #define works? I need to be able to flip the value of a #define variable, between true and false, within a method call. My attempts so far have been fruitless - it appears that when you type #define inline the program begins with the lowest down #define in the code. EG if I have:

Code:

---

#define TRUE 1;
#define FALSE 0;

#define variable TRUE;

if(condition) {
#undef variable;
#define variable FALSE;
}

---

My program will always begin with variable set to false.

Explanations appreciated!

#define is not used to define variables. #define is a simple command to the preprocessor to replace all the text it sees with the given value you provided.
In your example, it will replace every TRUE it finds with "1;".
Perhaps you should learn more about #defines, the preprocessor and variables.

Well, I haven't come to this forum as a first resort. I just want to know if it is possible to "re-point" a #define ?substitution rule? So, in my example, the program replaces all text "variable" with "TRUE" which is in turn replaced by 1. Is it possible to "re-point" variable at any point in the program? Or am I being a newb and going about this all the wrong way :s

It's possible, but not recommended. Whenever you do a a #define, the preprocessor will start replacing all the text from that point onwards. So you can do a "#define variable TRUE" somewhere and it will replace all the "variable" with "TRUE".
You can also undefine a define and then define it again, so you redefine it to something else.
But do not two things first:

- The preprocessor runs only once. So if you replace something with TRUE, then it will be TRUE in the code and not 1.
- Defines should not end with a ";". Everything after the space of the define is what the preprocessor will replace the text with.

So "#define TRUE 1;" will replace every "TRUE" with "1;" and not "1".

But surely then, as in my example, only the code following the #define will benefit from the change in the value?

What I want to be able to do is change a "global variable" during the running of the program; a "global variable" that a number of conditions are based upon. I don't think that a #define rule is going to do the trick here.

I really appreciate your help, you have confirmed my suspicions, but I don't know where to go from here.

I really want to type private boolean debugModeOn; :s

That's not a global variable in your code.

a global variable doesn't start with #define

If you have a global variable say:

int x = 10;

Then anywhere in the program you can change that value and it will be the stored and not lost. Also I'm interested to know what 'conditions' that you are talking about.

Well I've certainly learned that now. The implicit question was; "what is a global variable in C?".

EDIT:

Ah, ok, I see now. At any point during the running of my program debug mode can be turned on or off with user input. (That's the goal anyway!). I'll go and try this out.

A global variable is just a variable that is defined at global scope, ie outside any functions.

Code:

---

int myint;
int main()

---

myint is global.
But global variables should be avoided, if possible.

As to your original question, you suspicion is correct. Define is not suited for global variables. It is suited for constants and macros.

A global variable is a variable you declare outside a function typically before the main function. Unlike variables declared inside functions where the values are lost when the function exits, the global variable retains it's value between function calls.

So if you have defined x = 10 as an int globally. It will remain that way until changed, if changed, it will keep that change until the program exits.

Quote:

---

Originally Posted by Elysia

But global variables should be avoided, if possible.

---

Exactly. It's better to put use structs.

Eitherways, for small programs it doesn't matter about global variables and can be the most efficient way to implement a solution.

This may or may not be, but one should consider avoiding them since it's bad practice and will also make avoiding the decision of when the program is big enough to do away with them.
I don't recommend using them at all, unless necessary, not even in small programs. But your mileage may vary. Just take this into account.

Note also that the preprocessor does not do any sort of interpretation of just about anything that isn't starting with # or has a "name" in it that is a #define. So for example, we can write this (horrible thing):

Code:

---

#define A 1

int main()
{
    for(i = A;  // 1
#undef A
#define A 11
          i < A; i++)    // 2
    {
#undef A
#define A 100
          printf("i=%d A = %d\n", i, A);    // 3
   
    }
    return 0;
}

---

1. A is replaced with 1
2. A is replaced by 11
3. A is replaced by 100

--
Mats

I think I've found a solution;

Code:

---


int myLittleInt = 0;

#define debugOn myLittleInt
#define DEBUG debugOn

.....

switch(command)

case DEBUG: flipDebug(); break;

.....

void
flipDebug(void) {
if(1 == myLittleInt)
    myLittleInt = 0;
else
    myLittleInt = 1;
}



/*I know that I could probably just have #define DEBUG myLittleInt, but I want it like this for reasons that will be unapparent in this cut down example*/

---

Thanks for your help folks!

That's not going to work

This is not really a good idea (not to mention you can't switch in a non-constant expression). It's confusing to say the least. Instead, it's better to do something such as:

Code:

---

typedef int bool;
#define false 0
#define true 1
bool debug = true;

...
if (debug)
...

void flipDebug(void)
{
    debug = !debug;
}

---