Unexpected output of printf

by

You are passing a float for the %d format string, but printf is expecting an int.

printf is a variable argument list function: printf(const char *format_string,...);

This means that the rest of the arguments after the format string can be of any type and number, and the compiler doesn’t know what they should be. It is up to the programmer to provide arguments that are of the type that printf is expecting. What printf expects is determined by the format string. When you give a %d in your format string, the printf function is going to expect that the next argument is an int. Since you are passing a float, something strange is probably going to happen. For example, those bytes which make up the floating point number might be treated as if they were an int, which won’t give you any meaningful value.

Actually it is a little more complicated than that. There are special rules about how parameters are passed to variable argument functions. One of the rules is that float values are passed as doubles. Which means that your float value is first converted to a double before being passed to printf. Most likely a double is eight bytes on your platform, while an int is only four. So the printf function could be treating the first four bytes of your double value as an int.

What is perhaps even worse is that on the next line, an int is being passed where a double is expected. Which means that the printf function could treat the first four bytes of your int as part of the double, and then read four more bytes that weren’t even part of your arguments.

The details of what actually happens is platform-specific. The language simply states that you shouldn’t pass the wrong type of arguments and makes no guarantees about will happen if you do.

More Related Contents:

  1. printf(“%p”) and casting to (void *)
  2. printf specify integer format string for float
  3. C: Weird conditional printf behavior [closed]
  4. Function does not return printf
  5. decimal of numbers in c
  6. Why does printf not flush after the call unless a newline is in the format string?
  7. Printing leading 0’s in C
  8. printf format specifiers for uint32_t and size_t
  9. printf adds extra `FFFFFF` to hex print from a char array [duplicate]
  10. call printf using va_list
  11. Behaviour of printf when printing a %d without supplying variable name
  12. Why is printf with a single argument (without conversion specifiers) deprecated?
  13. Determining sprintf buffer size – what’s the standard?
  14. Are C-structs with the same members types guaranteed to have the same layout in memory?
  15. How to use “zd” specifier with `printf()`?
  16. Passing too many arguments to printf
  17. printf with “%d” of numbers starting with 0 (ex “0102”) giving unexpected answer (ex ‘”66″)
  18. Wrong format specifiers in scanf (or) printf
  19. Using printf with a non-null terminated string
  20. Casting one C structure into another
  21. What primitive data type is time_t? [duplicate]
  22. printf string, variable length item
  23. Is it possible to print out only a certain section of a C-string, without making a separate substring?
  24. Printf long long int in C with GCC?
  25. cross-platform printing of 64-bit integers with printf
  26. What precisely does the %g printf specifier mean?
  27. C Function to Convert float to byte array
  28. Turbo C++: Why does printf print expected values, when no variables are passed to it?
  29. Can I compare int with size_t directly in C?
  30. Is sprintf(buffer, “%s […]”, buffer, […]) safe?

Leave a Comment