I had a frustrating problem which turned out to be caused by the line

C Interview Questions and Answers

(Continued from previous question...)

I had a frustrating problem which turned out to be caused by the line

Q: I had a frustrating problem which turned out to be caused by the line
printf("%d", n);
where n was actually a long int. I thought that ANSI function prototypes were supposed to guard against argument type mismatches like this.

A: When a function accepts a variable number of arguments, its prototype does not (and cannot) provide any information about the number and types of those variable arguments. Therefore, the usual protections do not apply in the variable-length part of variable-length argument lists: the compiler cannot perform implicit conversions or (in general) warn about mismatches. The programmer must make sure that arguments match, or must manually insert explicit casts.
In the case of printf-like functions, some compilers (including gcc) and some versions of lint are able to check the actual arguments against the format string, as long as the format string is an immediate string literal.

(Continued on next question...)

Other Interview Questions

• Someone explained to me that arrays were really just constant pointers.
• There seem to be a few missing operators ...
• What is a good way to check for ``close enough'' floating-point equality?
• ow can I display a percentage-done indication that updates itself in place, or show one of those twirling baton progress indicators?
• Write down the equivalent pointer expression for referring the same element a[i][j][k][l]?
• How can I open files with names like ...
• My compiler isnt letting me declare a function
• How can I use a macro argument inside a string literal in the macro expansion?
• When does the compiler not implicitly generate the address of the first element of an array?
• I have got some code that is trying to unpack external structures
• More...