YOUR C LEARNING COMPANION

Kahan se padhein?

Learning path
Input ke saath kaamChapter 51 of 73

Formatted input: matching aur limits

Scanf destination contracts, assignment counts, field widths, whitespace aur numeric conversion limits padhein.

6 min readIntermediateC17 baseline
Offline reading
Is chapter mein8 sections

Formatted input text ko requested pattern se match karta hai. Call input ka sirf kuch hissa match kar sakti hai ya expected se kam values assign kar sakti hai. Values use karne se pehle return result aur destination limits samajhna zaroori hai.

1. Input ko destinations chahiye, output argument types nahi

scanf stdin se, fscanf selected stream se aur sscanf null-terminated input string se read karta hai. Input-conversion rules shared hain. Scalar destination ko usually address chahiye, jaise &number. Array name normally first element ke pointer mein convert hota hai, isliye %s ke character array ko word pass karein, &word nahi.

Conversionprintf valuescanf destination
%dintint *
%ldlonglong *
%zusize_tsize_t *
%fdoublefloat *
%lfdoubledouble *
%Lflong doublelong double *
%cintchar *
%sReadable string pointerSufficient space wala writable character array

Wrong type, insufficient storage ya ended lifetime wali destination contract violate karti hai. Variadic interface hidden buffer size supply nahi karta. printf ki float-to-double promotion scanf ke float pointer ko double pointer nahi banati. Declarations ke liye <stdio.h> include karein.

C17 · illustrative fragment
int number = 0;
char word[4];
int assigned = sscanf("12 cat", "%2d %3s", &number, word);

Controlled example ke two numeric input characters int mein safely representable hain. %3s at most three non-whitespace characters plus terminator store karta hai, isliye array mein four elements chahiye. Successful assignments count hote hain; expected count check karke results use karein. Partial match earlier destinations already modify kar sakta hai; caller ko all-or-nothing update chahiye toh temporary parse objects initialize karke use karein.

2. Field width consumption limit karti hai, poora record nahi

C17 · illustrative fragment
char first[4];
char second[4];
int assigned = sscanf("codedile", "%3s%3s", first, second);

First conversion word ka remainder next conversion ke liye available chhodti hai. Specified layout parse karne mein useful hai, par width-limited %s user ne short-enough word diya tha iska proof nahi. Remaining suffix next field ya next input attempt ban sakta hai. %c ki width utne characters request karti hai aur null terminator add nahi hota; %[ ko bhi appropriate width aur terminator ki space chahiye.

3. Format ki whitespace bhi instruction hai

C17 · illustrative fragment
char first = '?';
char second = '?';
int a = sscanf(" x", "%c", &first);
int b = sscanf(" x", " %c", &second);

Most conversions leading input whitespace skip karti hain; %c, %[ aur %n exceptions hain. Format ki whitespace input ki any amount whitespace, including newlines, consume karti hai jab tak next non-whitespace character ya input end na aaye. Isliye scanf("%d\n", &number) simply integer aur uski line finish karna nahi: interactive call later non-whitespace character ke liye wait kar sakti hai. Literal comma ya other ordinary format character ko input se match karna hota hai.

4. Matching failure aur input failure alag karein

C17 · illustrative fragment
int value = 99;
int mismatch = sscanf("cat", "%d", &value);
int input_end = sscanf("", "%d", &value);
int assigned = sscanf("12 34", "%*d %d", &value);

Matching failure mein available input conversion se fit nahi hota, jaise cat ko %d dena. Input failure mein input obtain nahi ho saka, jaise end-of-input ya read error. First conversion complete hone se pehle input failure par EOF return hota hai; otherwise return assignments ka count hai, jo zero bhi ho sakta hai. %*d jaisi assignment-suppressed conversions count increase nahi karti. Special %n conversion normally ab tak consumed characters ka count store karti hai, lekin uski assignment returned count mein included nahi.

Matching failure troublesome character unread chhod sakti hai. Input consume ya replace kiye bina same call repeat karna indefinitely same failure de sakta hai. Stream input failure ke baad error/end indicators inspect karein. Isi wajah se parse se pehle whole bounded line acquire karna interactive program ko clearer retry boundary deta hai.

5. Representability ab bhi aapki responsibility hai

C17 mein numeric scanf result destination object mein represent na ho toh undefined behavior hai. Baad mein return count check karna us event ko repair nahi kar sakta. Field width sirf characters bound karti hai; digits destination range exceed kar sakte hain aur user chosen width se longer token de sakta hai. External numeric text ke liye bounded line acquisition aur strtol/strtoul ya other suitable checked conversion prefer karein.

Primary references aur aage ki reading

Aage badhne se pehle

  • Formatted input partial match ya failed conversion par ruk sakti hai.
  • Destination types aur widths conversion contract aur storage se match hone chahiye.
  • scanf-family mein nonrepresentable numeric conversion ka special dhyaan chahiye.
In ideas ko alag rakhein
Characters consumed / Values assigned
Call input consume karke bhi expected destinations assign na kare; result inspect karein.
Apne words mein samjhaayein

First conversion ki success se poora requested input record accept hona kyun establish nahi hota?

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.

Counted conversion ka result use karne se pehle scanf return value kyun check karein?
Har choice ki explanation padhein
  1. Input conversion us result ko store karne se pehle fail ho sakti hai.

    ✓ Sahi reasoning. Results use karne se pehle expected counted assignments check karein; %n is count mein include nahi hota.

  2. scanf pehle har destination zero kar deta hai.

    Failed conversion destination ko zero initialize karne ka promise nahi karti.

  3. Width limit valid numeric range guarantee karti hai.

    Field width consumed input limit karti hai; yeh general numeric-range validation strategy nahi.

C17

Agla idea padhne ke liye tayyar?

Mark this chapter as read whenever you feel ready.

CHAPTER 51 / 73

Is chapter mein

Formatted input: matching aur limits

Search all 73 chapters in both languages.EN + HG

Try “pointer”, “why int”, or “undefined behavior”.

Concepts connect. Follow your curiosity.↑ ↓ to explore · Enter to open
MAKE YOURSELF COMFORTABLE

Your reading space

Appearance

A clear canvas with balanced contrast.

Text size

100%
AA

Reading tools

Your data stays in this browser

Export a backup before changing browsers or replacing an older version of the reader.

YOUR PERSONAL MARGINS

My notebook

Saved on this device
A LITTLE CLARITY

The glossary

A starting meaning, then a chapter to go deeper.

A QUICK DEFINITION

A little clarity

Read the full explanation →

A thought worth keeping