Of course, but the confusion lies in that it's a pre-processor. It finds and replaces all the instances of the text it can find. The preprocessor knows nothing about your code and cannot say whether it's intentional to place TEXT here or there.Originally Posted by MacGyver
It's so very easy to mess up. You can even define keywords:
Which is why I assumed that it changes all the text it finds.Code:#define float THIS IS WRONG float myvar; // Compile error: syntax error
It's defined to look and act like a function. Show me an example where you could have TEXT() with an argument given to it where the preprocessor should not handle it.
Don't know. If it doesn't replace any text, or strings, then the chances of it being too generic reduces drastically.
I think this is why CornedBee gave you the answer he did.
Yes, I can accept that answer.
The preprocessor is aware of what comments and string literals are. It won't replace inside those.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
