`getchar()` gives the same output as the input string

by

In the simple setup you are likely using, getchar works with buffered input, so you have to press enter before getchar gets anything to read. Strings are not terminated by EOF; in fact, EOF is not really a character, but a magic value that indicates the end of the file. But EOF is not part of the string read. It’s what getchar returns when there is nothing left to read.

More Related Contents:

  1. How to simulate an EOF?
  2. Why do I need to type Ctrl-D twice to mark end-of-file?
  3. I’m trying to understand getchar() != EOF
  4. Why Ctrl-Z does not trigger EOF?
  5. why the program is not terminating in gcc? [closed]
  6. Why is “while ( !feof (file) )” always wrong?
  7. How to avoid pressing Enter with getchar() for reading a single character only?
  8. What is the equivalent to getch() & getche() in Linux?
  9. Why doesn’t getchar() wait for me to press enter after scanf()?
  10. What is EOF in the C programming language?
  11. End of File (EOF) in C
  12. Why is “while( !feof(file) )” always wrong?
  13. How to use EOF to run through a text file in C?
  14. setvbuf not able to make stdin unbuffered
  15. EOF in Windows command prompt doesn’t terminate input stream
  16. How to clear stdin before getting new input?
  17. fgetc, checking EOF
  18. Comparing unsigned char and EOF
  19. int c = getchar()?
  20. getchar does not stop when using scanf
  21. Representing EOF in C code?
  22. Why do I require multiple EOF (CTRL+Z) characters?
  23. Using getchar() in a while loop
  24. Having troubles with EOF on Windows 7
  25. Why do i have to input EOF 3 times when using fgets?
  26. How do you read scanf until EOF in C?
  27. Using getchar() on c gets the ‘Enter’ after input [duplicate]
  28. Function declaration: K&R vs ANSI [duplicate]
  29. C Macros to create strings
  30. Why does a=(b++) have the same behavior as a=b++?

Leave a Comment