Streams, buffering aur EOF
Stream state, standard streams, buffering, read results aur end-of-file versus error samjhein.
Is chapter mein8 sections
C input-output mein streams use hoti hain. Stream program ko characters ki sequence se jodti hai; buffering se underlying device tak work pahunchne mein delay ho sakta hai. Read results follow karke end-of-file aur error alag samjhenge.
1. Stream data aur state carry karta hai
Stream C library ka input/output abstraction hai. FILE object stream control ki information record karta hai, jaise buffering, position aur status. FILE * documented functions se use karein; FILE object copy karne se independent open stream nahi milti. Stream filename ya operating-system file descriptor se bhi different hai.
- Program interface
- fgetc / fgets / fprintf / fread
- Library state
- Buffer, position, end aur error indicators
- External destination
- Terminal, file ya other supported connection
Hosted startup par stdin, stdout aur stderr already open milte hain. Convention mein ordinary results stdout aur diagnostics stderr par jaate hain, taaki environment separately route kar sake. Names particular devices guarantee nahi karte. Is unit ke examples byte-oriented I/O use karte hain; same oriented stream par wide-character aur byte I/O casually mix na karein.
2. Read attempt karke result inspect karein
#include <stdio.h>
#include <stdlib.h>
int main(void)
{
int ch;
while ((ch = getchar()) != EOF) {
if (putchar(ch) == EOF) return EXIT_FAILURE;
}
if (ferror(stdin)) return EXIT_FAILURE;
if (fflush(stdout) == EOF) return EXIT_FAILURE;
return EXIT_SUCCESS;
}
getchar int return karta hai, char nahi. Successful byte input unsigned-char value ka int conversion hai; EOF sentinel ke liye negative integer constant hai. Test tak result int mein rakhein. EOF ka matlab file mein stored special visible character nahi. Loop har input operation check karta hai; while (!feof(stdin)) se next read predict nahi karta.
EOF return end-of-file ya read error signal kar sakta hai. Yahan ferror error case distinguish karta hai. Output aur final flush bhi checked hain, kyunki library buffer mein accepted data transmit hote waqt fail ho sakta hai. Checked target ka int har unsigned char value represent kar sakta hai; unusual narrower-int-value-range targets par converted input aur EOF distinguish karne mein extra care chahiye.
3. Buffering call aur external delivery alag karti hai
| Mode | Useful model |
|---|---|
| Unbuffered | Characters as soon as possible appear karne ke intended hain. |
| Line buffered | Stream rules ke subject newline par characters block ki tarah transmit hone ke intended hain. |
| Fully buffered | Characters block transmission ke liye collect ho sakte hain, jaise buffer fill hone par. |
Initially stderr fully buffered nahi; unbuffered hona specifically required nahi. Implementation determine kar sake ki standard input/output interactive nahi hain, tab woh fully buffered hote hain. stdout ko always line buffered na kahein. Newline har destination ko physical storage force karne ki universal request bhi nahi.
4. Wait karne se pehle output prompt flush karein
#include <stdio.h>
#include <stdlib.h>
int main(void)
{
if (fputs("Name: ", stdout) == EOF) return EXIT_FAILURE;
if (fflush(stdout) == EOF) return EXIT_FAILURE;
char name[20];
if (fgets(name, sizeof name, stdin) == NULL) return EXIT_FAILURE;
if (fputs("Received input.\n", stdout) == EOF) return EXIT_FAILURE;
return fflush(stdout) == EOF ? EXIT_FAILURE : EXIT_SUCCESS;
}
Prompt mein newline nahi, isliye read se pehle program explicitly fflush(stdout) call karta hai. Yeh library ko unwritten output host environment tak deliver karne ko kehta hai; portable disk-durability guarantee nahi. Small example sirf first input chunk acknowledge karta hai. Iska claim nahi ki fgets ne complete name read ya contents validate kar diye; line-input lesson un questions ko handle karta hai.
5. Indicators events remember karte hain
#include <assert.h>
#include <stdio.h>
#include <stdlib.h>
int main(void)
{
FILE *stream = tmpfile();
if (stream == NULL) return EXIT_FAILURE;
int ch = fgetc(stream);
assert(ch == EOF);
assert(feof(stream) != 0);
assert(ferror(stream) == 0);
clearerr(stream);
assert(feof(stream) == 0 && ferror(stream) == 0);
return fclose(stream) == EOF ? EXIT_FAILURE : EXIT_SUCCESS;
}
Temporary stream empty start hoti hai. Failed read ke baad hi end-of-file indicator set hota hai. Indicators tab tak persist karte hain jab tak specified clearing behavior wali operation unhe change na kare. clearerr EOF aur error indicators clear karta hai; underlying problem repair ya position change nahi karta. EOF indicator clear karne se more input create nahi hota. fflush(stdin) avoid karein: portable C ise input-discard operation define nahi karti.
Primary references aur aage ki reading
- WG14 N1570 — public C11 committee draft: 7.21.1–7.21.3, 7.21.5.2, 7.21.7, 7.21.10. C17 baseline ke stable core provisions ke liye; final ISO publication nahi.
Aage badhne se pehle
- Stream sequence ka C interface hai; underlying device se alag hai.
- Read result check karne ke baad hi use character samjhein.
- Buffering, end-of-file indicator aur error indicator ke meanings alag hain.
In ideas ko alag rakhein
- EOF result / End-of-file state
- Read end-of-file ya error ki wajah se EOF de sakti hai; indicators se difference check karein.
Character read ko char mein narrow karne se pehle int mein store aur check kyun karenge?
Optional: bolkar samjhein ya note rakhein. Tayyar hon toh aage badh sakte hain.Apni understanding check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Kyunki int hamesha exactly ek visible letter store karta hai.
Purpose function ka return interface preserve karna hai, universal letter representation nahi.
- Jaldi char conversion se return-value check ki required information kho sakti hai.
✓ Sahi reasoning. Return type preserve karein aur interface ke according stream ka EOF/error state inspect karein.
- EOF har file ke end par stored extra character hai.
EOF interface ka integer indicator hai, required stored file character nahi.
C17
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.