Is scanf(“%d%d”, &x, &x) well defined?

by

The short answer is: Yes, it is defined:

scanf will attempt to convert a sequence of bytes from stdin as an integer written in base 10 with optional initial spaces and an optional sign. If successful, the number will be stored into x. scanf will then perform these steps a second time. The return value can be EOF, 0, 1 or 2, and for the latter 2, the last number converted will have been stored into x.

The long answer is somewhat more subtile:

It seems the C Standard does specify that the values are stored in the order of the format string. Quoting the C11 Standard:

7.21.6.2 The fscanf function

…

4 The fscanf function executes each directive of the format in turn. When all directives have been executed, or if a directive fails (as detailed below), the function returns.

…

7 A directive that is a conversion specification defines a set of matching input sequences, as described below for each specifier. A conversion specification is executed in the following steps:

…

10 Except in the case of a % specifier, the input item (or, in the case of a %n directive, the count of input characters) is converted to a type appropriate to the conversion specifier. If the input item is not a matching sequence, the execution of the directive fails: this condition is a matching failure. Unless assignment suppression was indicated by a *, the result of the conversion is placed in the object pointed to by the first argument following the format argument that has not already received a conversion result.

…

16 The fscanf function returns the value of the macro EOF if an input failure occurs before the first conversion (if any) has completed. Otherwise, the function returns the number of input items assigned, which can be fewer than provided for, or even zero, in the event of an early matching failure.

Nowhere else in this specification are any accesses to the output objects even mentioned.

Yet the wording of the Standard seems to indicate that if 2 pointers point to the same object, the behavior might be unexpected: the result of the conversion is placed in the object pointed to by the first argument following the format argument that has not already received a conversion result. This phrase is somewhat ambiguous: what does that has not already received a conversion result refer to? the object or the argument? Objects receive conversion results, not the pointer arguments. In your contorted example, the object x has already received a conversion result, so it should not receive another one… But as noted by supercat, this interpretation is overtly restrictive as it would imply that all converted values be stored into the first target object.

So it appears fully specified and well defined, but the wording of the specification could be perfected to remove a potential ambiguity.

More Related Contents:

  1. What are the valid signatures for C’s main() function?
  2. Are there any non-twos-complement implementations of C?
  3. What is the behavior of printing NULL with printf’s %s specifier?
  4. Does printf(“%x”,1) invoke undefined behavior?
  5. Representation of negative numbers in C?
  6. How undefined is undefined behavior?
  7. Does &((struct name *)NULL -> b) cause undefined behaviour in C11?
  8. Can code that will never be executed invoke undefined behavior?
  9. Is argv[n] writable?
  10. Is it guaranteed to be safe to perform memcpy(0,0,0)?
  11. Is `*((*(&array + 1)) – 1)` safe to use to get the last element of an automatic array?
  12. Is fgets() returning NULL with a short buffer compliant?
  13. Can an equality comparison of unrelated pointers evaluate to true?
  14. Why “initializer element is not a constant” is… not working anymore?
  15. Is int main() { } (without “void”) valid and portable in ISO C?
  16. How do I make an infinite empty loop that won’t be optimized away?
  17. How are multiple prior declarations resolved for a new declaration with extern?
  18. When is it valid to access a pointer to a “dead” object?
  19. Returning struct containing array
  20. Can the following code be true for pointers to different things
  21. Is it Undefined Behaviour to cast away the constness of a function parameter?
  22. Which section in C89 standard allows the “implicit int” rule?
  23. Is it undefined behavior to redefine a standard name?
  24. C – is an indeterminate value indeterminable?
  25. Why can’t a modifiable lvalue have an array type?
  26. How a stream error indicator affects following input code?
  27. Initialization vs Assignment in C
  28. How to compile a static library in Linux?
  29. How to get the length of a function in bytes?
  30. What happens to memory after free()?

Leave a Comment