|
I thought I would check errno after a long string of printf calls
C Interview Questions and Answers
(Continued from previous question...)
I thought I would check errno after a long string of printf calls
Q: I thought I'd check errno after a long string of printf calls, to see if any of them had failed:
errno = 0;
printf("This\n");
printf("is\n");
printf("a\n");
printf("test.\n");
if(errno != 0)
fprintf(stderr, "printf failed: %s\n", strerror(errno));
Why is it printing something strange like ``printf failed: Not a typewriter'' when I redirect the output to a file?
A: Many implementations of the stdio package adjust their behavior slightly if stdout is a terminal. To make the determination, these implementations perform some operation which happens to fail (with ENOTTY) if stdout is not a terminal. Although the output operation goes on to complete successfully, errno still contains ENOTTY. This behavior can be mildly confusing, but it is not strictly incorrect, because it is only meaningful for a program to inspect the contents of errno after an error has been reported. (More precisely, errno is only meaningful after a library function that sets errno on error has returned an error code.)
In general, it's best to detect errors by checking a function's return value. To check for any accumulated error after a long string of stdio calls, you can use ferror.
(Continued on next question...)
Other Interview Questions
| 