Problem with getchar()

I am writing the following program:

Code:

---


//Prints a table of squares using a for statement

#include <stdio.h>
#include <stdbool.h>

int main (int argc, const char * argv[]) {
    // insert code here...
    //declarations
        int i, n;
       
        printf("This program prints a table of squares.\n");
        printf("Enter number of entries in table: ");
        scanf("%d", &n);
       
        for (i = 1; i <= n; i++) {
                printf("%10d%10d\n", i, i * i);
               
                if (i % 24 == 0){
                        printf("Press Enter to continue...");
                        if (getchar() == '\n')
                                continue;
                }
                                       
        }
       
        return 0;
}

---

The problem is that the program does not wait for user to press the enter in the first 24 group of numbers.It waits only after the second group.Probably in the first getchar() execution there is a new line character in the buffer.
Any ideas on how to handle this?
Thank you.

Quote:

---

Originally Posted by skiabox

Probably in the first getchar() execution there is a new line character in the buffer.
Any ideas on how to handle this?

---

Yeah, that's exactly what's happening - scanf() isn't reading it in, so it's left there for the first getchar() to find.

Simplest way I can think of is to just add a call to getchar() after your scanf() call.

I did that and it worked!
Thank you very much for your help!:)

Your analysis of the problem is accurate. Just clear out any left over characters in the stream if scanf succeeds:

Code:

---

if (scanf("%d", &n) == 1) {
    while (getchar() != '\n')
        ;
}
else {
    /* Input failed, handle the error */
}

---

>Simplest way I can think of is to just add a call to getchar() after your scanf() call.
Simplest, yes. But a single call to getchar may or may not work depending on the contents of the stream. It's generally not a good idea to assume the next character is always a newline, so I recommend the slightly less simple loop above.