The need for parentheses in macros in C [duplicate]

by

Pre-processor macros perform text-replacement before the code is compiled so
SQR(b+5) translates to
(b+5*b+5) = (6b+5) = 6*3+5 = 23

Regular function calls would calculate the value of the parameter (b+3) before passing it to the function, but since a macro is pre-compiled replacement, the algebraic order of operations becomes very important.

More Related Contents:

  1. C macros and use of arguments in parentheses
  2. Overloading Macro on Number of Arguments
  3. Real-world use of X-Macros
  4. Macro definition to determine big endian or little endian machine?
  5. Are typedef and #define the same in c?
  6. What exactly do C include guards do?
  7. Array-size macro that rejects pointers
  8. What are C macros useful for?
  9. Is there a good reason for always enclosing a define in parentheses in C?
  10. Opposite of C preprocessor “stringification”
  11. C Macros to create strings
  12. Macro and function with same name
  13. offsetof at compile time
  14. Macros to create strings in C
  15. How to pass arguments in __VA_ARGS to a 2d character array? [closed]
  16. Is it possible to iterate over arguments in variadic macros?
  17. How, exactly, does the double-stringize trick work?
  18. What is “:-!!” in C code?
  19. Shall I prefer constants over defines?
  20. Macro returning the number of arguments it is given in C? [duplicate]
  21. What do the parentheses around a function name mean?
  22. Seeing expanded C macros
  23. Indenting #defines
  24. How big can a malloc be in C?
  25. What are the implications of the linux __user macro?
  26. Why does #define not require a semicolon?
  27. Incompatible pointer types passing in _Generic macro
  28. C# Macro definitions in Preprocessor
  29. Are constant C expressions evaluated at compile time or at runtime?
  30. Changing a macro at runtime in C

Leave a Comment