With C/C++ macros it's quite easy to generated long constructs automatically. For example, if I want a huge set of methods to not ever throw exceptions (a must for COM-exposed methods) I can do something like this:
#define BEGIN_COM_METHOD\
try{
#define END_COM_METHOD\
return S_OK;\
} catch( exception& ) {\
// set IErrorInfo here\
return E_FAIL;\
}
to make such macros manageable one can use "\" character to make the macro definition multiline and more readable.
The problem is sometimes code with such constructs will not compile - something will not expand as expected and invalid code will be present to the compiler. Compiler usually have "generate preprocessed file" option to show the developer the preprocessing result. But in the preprocessed file the macro is expanded into one line and the result is barely readable.
Is it possible to make the preprocessor to keep the linebreaks present in the macro definition?
__LINE__ is a preprocessor macro that expands to current line number in the source file, as an integer. __LINE__ is useful when generating log statements, error messages intended for programmers, when throwing exceptions, or when writing debugging code.
## is Token Pasting Operator. The double-number-sign or "token-pasting" operator (##), which is sometimes called the "merging" operator, is used in both object-like and function-like macros.
The number-sign or "stringizing" operator (#) converts macro parameters to string literals without expanding the parameter definition. It's used only with macros that take arguments.
Token Pasting / Token Concatenation: It is often useful to merge two tokens into one while expanding macros. This is called token pasting or token concatenation. The '##' preprocessing operator performs token pasting.
You can't do it. The replacement text is until the end of the line where it is #define
d, so it will not have newlines in it. If your problems with compilation are infrequent, you could run the preprocessed file through indent
or something like that before compiling when that happens to help you get more readable code.
This is not possible since the \
characters are removed in phase 2, before the preprocessor is involved. See the question Poster with the 8 phases of translation in the C language for a list of the phases of translation.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With