cunixstdioungetc

ungetc: number of bytes of pushback

ungetc is only guaranteed to take one byte of pushback. On the other hand, I've tested it on Windows and Linux and it seems to work with two bytes.

Are there any platforms (e.g. any current Unix systems) on which it actually only takes one byte?

Solution

  • 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' — and the same on Solaris 11.3. Worse, on HP-UX 11.00 (PA-RISC), HP-UX 11.23 (Itanium), and HP-UX 11.31 (Itanium), I got an error at 'count = 1' - belying the theory that 2 is safe. Similarly, AIX 6.0 (and 7.2) gave an error at 'count = 1'.

    Summary

    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).

    In December 2023, the program above failed at count = 1 on Windows Server 2016 Standard using MSVC 19.15.26730 for x64. This is different from what rwallace found.