May 14, 2011 · What is the point of #define in C++? I've only seen examples where it's used in place of a "magic number" but I don't see the point in just giving that value to a variable instead.

The question is if users can define new macros in a macro, not if they can use macros in macros.

15 Without boost : define same macro again and compiler itself will give warning. From warning you can see location of the previous definition. vi file of previous definition .

For example, never define a macro like this: #define DANGER 60 + 2 This can potentially be dangerous when we do an operation like this: int wrong_value = DANGER * 2; // Expecting 124 Instead, def...

The #define directive is a preprocessor directive; the preprocessor replaces those macros by their body before the compiler even sees it. Think of it as an automatic search and replace of your source code. …

I want to write a macro that spits out code based on the Boolean value of its parameter. So say DEF_CONST(true) should be expanded into const, and DEF_CONST(false) should be expanded …

Oct 28, 2009 · Is it better to use static const variables than #define preprocessor? Or does it maybe depend on the context? What are advantages/disadvantages for each method?

How do I define a function with optional arguments? Asked 14 years, 1 month ago Modified 1 year, 9 months ago Viewed 1.2m times

Nov 4, 2009 · Which one is better to use among the below statements in C? static const int var = 5; or #define var 5 or enum { var = 5 };

Dec 21, 2011 · If I have: #define MAXLINE 5000 What type is MAXLINE understood to be? Should I assume it is an int? Can I test it somehow? In general, how can one determine the type of #defineed …