Why do I need this line of code?

this program works, but if I take out the while loop the program will end immediately after the last scanf(); I'm not sure why and would appreciate if someone could explain exactly why.

Code:

#include <stdio.h>

#define STORE_NAME "Sierra Sporting Goods"


int main(void){
    int intNumber, intType, intQuantity;
    double dblCost, dblPrice;
    
    printf("%s\n", STORE_NAME);
    printf("Enter the product number: ");
    scanf("%d", &intNumber);
    printf("\nEnter the product type: ");
    scanf("%d", &intType);
    printf("\nEnter the quantity: ");
    scanf("%d", &intQuantity);
    printf("\nEnter the cost: ");
    scanf("%lf", &dblCost);
    printf("\nEnter the price: ");
    scanf("%lf", &dblPrice);


    printf("\n\nThe product number is %d", intNumber);
    printf("\nThe product type is %d", intType);
    printf("\nThe quantity type is %d", intQuantity);
    printf("\nThe cost is %lf", dblCost);
    printf("\nThe price is %lf", dblPrice);
    
    printf("\nPress enter to continue\n");
    
    while(getchar() != '\n');              /*clear the buffer*/
    
    getchar();
  
   
 return 0;
    
}

The program will not end immediately after the scanf -- it will end at the line "return 0;" at the bottom. The key to remember is that scanf does not eat enter keys after input -- so when you get to "press enter to continue", you've already pressed enter before (when you typed in the price), so the program doesn't stop. The while loop specifically eats an enter key (the \n symbol) so that you "see" the results and the getchar() after it.

Edit: Note that if you run your program the way nature intended -- at the command line -- you wouldn't see any problems.

Originally Posted by tabstop

The program will not end immediately after the scanf -- it will end at the line "return 0;" at the bottom. The key to remember is that scanf does not eat enter keys after input -- so when you get to "press enter to continue", you've already pressed enter before (when you typed in the price), so the program doesn't stop. The while loop specifically eats an enter key (the \n symbol) so that you "see" the results and the getchar() after it.

Edit: Note that if you run your program the way nature intended -- at the command line -- you wouldn't see any problems.

Thanks for response. So without the while loop, the getchar() would get the \n instead of pausing like I had intended. I get it.

About your last sentence- Are you saying that if I ran it from the command line I wouldn't have to use the while loop?

Thats correct.

More specifically, while your program would end right away even on the command line, it wouldn't matter because you'd still be able to see the output, which I assume is your goal.

Ohhh right. I see. Thanks.

whatever you enter from keyboard will be stored in stdin buffer.. by using fflush(stdin) also u can perform the same thing that u did using while loop and getchar.. if fflush donot work then __fpurge(stdin) will definitely work.

Flushing stdin is undefined.
__fpurge is some non-standard crap.
Don't use either.

what are the problems of using fflush() and __fpurge() functions. why cant we use them?

Originally Posted by vapanchamukhi

what are the delimitation of using fflush() and __fpurge() functions. why cant we use them?

fflush is perfectly fine for output files, but for input files, fflush is officially undefined, so using it can cause ANYTHING to happen, it could "write 'Bang! You die!' on the console'", or it could crash your application, and it is DEFINITELY not in any way guaranteed to flush pending input.

--
Mats

Originally Posted by vapanchamukhi

what are the problems of using fflush() and __fpurge() functions. why cant we use them?

__fpurge() is a non-standard function, meaning that the code is not portable. If I took that file with the __fpurge() call I wouldn't be able to compile it.

QuantumPete