ungetc: number of bytes of pushback

by

The C99 standard (and the C89 standard before that) said unequivocally:

One character of pushback is guaranteed. If the ungetc function is called too many
times on the same stream without an intervening read or file positioning operation on that
stream, the operation may fail.

So, to be portable, you do not assume more than one character of pushback.

Having said that, on both MacOS X 10.7.2 (Lion) and RHEL 5 (Linux, x86/64), I tried:

#include <stdio.h>
int main(void)
{
    int i;
    for (i = 0; i < 4096; i++)
    {
        int c = i % 16 + 64;
        if (ungetc(c, stdin) != c)
        {
            fprintf(stderr, "Error at count = %d\n", i);
            return(1);
        }
    }
    printf("No error up to count = %d\n", i-1);
    return(0);
}

I got no error on either platform. By contrast, on Solaris 10 (SPARC), I got an error at ‘count = 4’. Worse, on HP-UX 11.00 (PA-RISC) and HP-UX 11.23 (Itanium), I got an error at ‘count = 1’ – belying the theory that 2 is safe. Similarly, AIX 6.0 gave an error at ‘count = 1’.

Summary

  • Linux: big (4 KiB)
  • MaxOS X: big (4 KiB)
  • Solaris: 4
  • HP-UX: 1
  • AIX: 1

So, AIX and HP-UX only allow one character of pushback on an input file that has not had any data read on it. This is a nasty case; they might provide much more pushback capacity once some data has been read from the file (but a simple test on AIX adding a getchar() before the loop didn’t change the pushback capacity).

More Related Contents:

  1. ‘ ‘, ‘\n’ , scanf() and output screen
  2. How to make child process die after parent exits?
  3. Differences between fork and exec
  4. What are the rules of automatic stdout buffer flushing in C?
  5. How to get the current directory in a C program?
  6. How to capture Control+D signal?
  7. What’s the best way to return a random line in a text file using C?
  8. how to control popen stdin, stdout, stderr redirection?
  9. What does the brk() system call do?
  10. Is there a Windows equivalent to fdopen for HANDLEs?
  11. Re-opening stdout and stdin file descriptors after closing them
  12. Using SO_REUSEADDR – What happens to previously open socket?
  13. Turn a simple socket into an SSL socket
  14. What are .a and .so files?
  15. Are there any platforms where using structure copy on an fd_set (for select() or pselect()) causes problems?
  16. How can I convert a file pointer ( FILE* fp ) to a file descriptor (int fd)?
  17. how to convert datetime to unix timestamp in c?
  18. Are file descriptors shared when fork()ing?
  19. Detecting 64bit compile in C
  20. What is the difference between getch() and getchar()?
  21. Is it necessary to reset the fd_set between select system call?
  22. fd leak, custom Shell
  23. Writing to stdin and reading from stdout (UNIX/LINUX/C Programming)
  24. *nix select and exceptfds/errorfds semantics
  25. Questions about putenv() and setenv()
  26. whitespace in the format string (scanf)
  27. Reading from stdin
  28. Tried and true simple file copying code in C?
  29. longjmp() from signal handler
  30. Why can’t I ignore SIGSEGV signal?

Leave a Comment