Why can’t I use sizeof in a preprocessor condition?

by

Because sizeof is evaluated at compilation time while directives are evaluated before compilation, and the part that does that is not the compiler, so it won’t understand what sizeof means.

More Related Contents:

  1. Why isn’t the size of an array parameter the same as within main?
  2. C sizeof a passed array [duplicate]
  3. Overloading Macro on Number of Arguments
  4. C macros and use of arguments in parentheses
  5. Should I use #include in headers?
  6. Are there any platforms where pointers to different types have different sizes?
  7. Why does sizeof(x++) not increment x?
  8. How to make a variadic macro (variable number of arguments)
  9. Is it possible to iterate over arguments in variadic macros?
  10. “#include” a text file in a C program as a char[]
  11. How to write a while loop with the C preprocessor?
  12. Including one C source file in another?
  13. How, exactly, does the double-stringize trick work?
  14. What exactly do C include guards do?
  15. Array-size macro that rejects pointers
  16. Can gcc output C code after preprocessing?
  17. Why does the C preprocessor interpret the word “linux” as the constant “1”?
  18. Shall I prefer constants over defines?
  19. Macro returning the number of arguments it is given in C? [duplicate]
  20. Is dereferencing null pointer valid in sizeof operation [duplicate]
  21. Seeing expanded C macros
  22. What are C macros useful for?
  23. How to get the string size in bytes?
  24. Opposite of C preprocessor “stringification”
  25. C – SizeOf Pointers
  26. Sizeof vs Strlen
  27. Pseudo-generics in C
  28. What is the possible use for “#define for if (false) {} else for”?
  29. Is there any reason not to use fixed width integer types (e.g. uint8_t)?
  30. why sizeof(‘a’) is 4 in C? [duplicate]

Leave a Comment