Indenting #defines

by

Pre-ANSI C preprocessor did not allow for space between the start of a line and the “#” character; the leading “#” had to always be placed in the first column.

Pre-ANSI C compilers are non-existent these days. Use which ever style (space before “#” or space between “#” and the identifier) you prefer.

http://www.delorie.com/gnu/docs/gcc/cpp_48.html

More Related Contents:

  1. The need for parentheses in macros in C [duplicate]
  2. #define macro for debug printing in C?
  3. #pragma pack effect
  4. Overloading Macro on Number of Arguments
  5. Should I use #include in headers?
  6. Real-world use of X-Macros
  7. Easy way to use variables of enum types as string in C?
  8. How to make a variadic macro (variable number of arguments)
  9. MIN and MAX in C
  10. How do I check OS with a preprocessor directive?
  11. Stringification of a macro value
  12. “#include” a text file in a C program as a char[]
  13. What is the meaning of lines starting with a hash sign and number like ‘# 1 “a.c”‘ in the gcc preprocessor output?
  14. Macro vs Function in C
  15. How to compare strings in C conditional preprocessor-directives
  16. What exactly do C include guards do?
  17. Understanding container_of macro in the Linux kernel
  18. Why does the C preprocessor interpret the word “linux” as the constant “1”?
  19. What does ## mean for the C(C++) preprocessor?
  20. Finding out what the GCC include path is [duplicate]
  21. Type of #define variables
  22. How can I autoformat/indent C code in vim?
  23. What are C macros useful for?
  24. Opposite of C preprocessor “stringification”
  25. Why does #define not require a semicolon?
  26. C circular dependency
  27. Pseudo-generics in C
  28. What is the possible use for “#define for if (false) {} else for”?
  29. Are constant C expressions evaluated at compile time or at runtime?
  30. Changing a macro at runtime in C

Leave a Comment