Ideas ko phir
saaf dekhein.
Har chapter ka recap, important distinction aur optional concept check. Apne bookmarks se revise karein ya koi topic baad ke liye choose karein.
Revision choices optional hain aur is browser mein rehti hain. Chapter read status aap separately choose karte hain.
Is view mein koi topic nahi. Filters reset karke baaki topics dekhein.
01Programming kya hai?Abhi choice nahi
Teen ideas yaad karein
- Specification allowed inputs, required results aur failure rules batati hai.
- Algorithm method describe karta hai; program work ko language mein express karta hai.
- Successful build se intended problem solve hona establish nahi hota.
C likhne se pehle canteen bill ke rules kaise describe karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Computer specified operations follow karta hai, isliye missing decisions explicit hone chahiye.
✓ Sahi reasoning. Program ko handled situations ke rules chahiye; unstated intention instruction nahi hai.
- Computer hamesha programmer ka intention guess karta hai.
Programmer ka intended meaning language rules ko replace nahi karta.
- Precise instructions har program correct bana deti hain.
Precision plan express karti hai, par plan mein phir bhi mistake ho sakti hai.
General
Related ideas dekhein
Pehle ke ideas
Koi earlier chapter required nahi. Chapter guide mein background assumptions dekhein.
Aage kahan use hota hai
02Computer instructions kaise follow karta haiAbhi choice nahi
Teen ideas yaad karein
- State program ki current situation describe karne wali information hai.
- Trace selected steps aur state par unke effects record karta hai.
- Finish hone wale loop ko exit tak pahunchne ka reason chahiye.
Four se five hokar rukne wale counter ko explain karne ke liye kya record karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, line breaks processor operations define karte hain.
Source layout one-to-one instruction count establish nahi karta.
- Haan, har comment ke liye ek machine instruction required hai.
Comments runtime instructions nahi hain.
- Nahi. Translation aur optimization alag arrangement bana sakti hain.
✓ Sahi reasoning. Particular machine-level trace assume karne se pehle language semantics se reason karein.
General
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
03CPU, memory, storage aur operating systemAbhi choice nahi
Teen ideas yaad karein
- Processor, working memory, storage aur operating system ke roles alag hain.
- Running process ki state stored executable file se alag hai.
- Working value badalne ke alawa data save karne ke liye suitable successful operation chahiye.
Same program ki do running copies different current values kyun dikha sakti hain?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- RAM aur persistent storage interchangeable hain.
Working memory aur persistent storage ke roles aur persistence alag hain.
- Working memory aur persistent storage ke roles alag hain.
✓ Sahi reasoning. Save karna normally persistent storage mein data likhta hai; working memory mein value rakhna alag operation hai.
- CPU har intermediate value permanently save karta hai.
Operations execute hone se har value ki persistent copy automatically nahi banti.
General
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
04Programming languages kyun hoti hainAbhi choice nahi
Teen ideas yaad karein
- Programming language work express karne ki notation aur rules deti hai.
- Syntax, meaning aur implementation strategy alag questions ke answers hain.
- C types aur interfaces work organise karte hain aur kuch explicit responsibilities programmer par rehti hain.
int ka meaning poochhne wale ko size discuss karne se pehle kya explain karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan. Grammar follow karna intended logic prove nahi karta.
✓ Sahi reasoning. Syntax, language meaning aur problem requirements alag sawaal hain.
- Nahi, grammar har real-world requirement check karti hai.
Parser har intended requirement nahi jaanta.
- Nahi, accepted code har input par intended answer zaroor dega.
Sirf acceptance aisi correctness guarantee nahi hai.
General
Related ideas dekhein
Aage kahan use hota hai
05C kyun banayi gayiAbhi choice nahi
Teen ideas yaad karein
- C earlier language ideas aur practical Unix systems work ke saath develop hui.
- Types aur structured operations se machine-specific instructions se aage systems data express hua.
- Portability language guarantees aur documented environment assumptions par depend karti hai.
Unix ke liye C kaunsi problem solve karne mein useful thi, aur har C program automatically portable kyun nahi hua?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Unix samet systems software implement karna.
✓ Sahi reasoning. C, Unix ke saath develop hua aur earlier systems-language work se aage badha.
- Har program ko har machine par unchanged chalane ki guarantee.
C ki history program ki implementation aur environment assumptions nahi hataati.
- Har machine-specific operation ko automatic safety checks se replace karna.
C mein bounds, lifetimes aur interfaces par explicit dhyaan dena padta hai.
General
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
06Source code se running program takAbhi choice nahi
Teen ideas yaad karein
- Source save karna, program build karna aur run karna alag actions hain.
- Headers translation information dete hain; required definitions phir bhi supply karni hoti hain.
- Executable successful build ke baad runtime resource missing hone se fail ho sakta hai.
Translate hone ke baad missing function definition se fail hone wale program ko kaise explain karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Complete executable body.
Declaration interface describe karti hai; body definition hoti hai.
- Linking successful hone ki guarantee.
Build ko program ki required definitions phir bhi chahiye.
- Function ke uses check karne ki information.
✓ Sahi reasoning. Suitable declaration calls check karne mein help karti hai, par missing body nahi deti.
C17
Related ideas dekhein
07Variables, values aur typesAbhi choice nahi
Teen ideas yaad karein
- Naam, object, uska type aur current value alag ideas hain.
- Initialisation starting value deti hai; later assignment doosri suitable value store karti hai.
- Integer value copy karne se objects ki future values permanently connect nahi hoti.
apples ki value saved mein copy karne ke baad apples badle toh saved unchanged kyun reh sakta hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- saved automatically apples follow karta hai.
Initializer ne int value copy ki thi; objects ke beech live connection nahi banaya.
- saved apni copied value rakhta hai jab tak use separately badla na jaaye.
✓ Sahi reasoning. Objects alag hain. Ek ko badalne se doosre ko assignment nahi hoti.
- saved exist karna band kar deta hai.
apples ko assignment dene se saved ki lifetime end nahi hoti.
C17
Related ideas dekhein
Pehle ke ideas
Koi earlier chapter required nahi. Chapter guide mein background assumptions dekhein.
08Data types, ranges aur representationsAbhi choice nahi
Teen ideas yaad karein
- Types values, operations, ranges, conversions aur storage requirements ke rules dete hain.
- Unsigned wrapping aur ordinary signed overflow ke rules alag hain.
- Exact limits ke liye C byte aur floating formats ki implementation properties check karni hoti hain.
Counts aur measured lengths ke types choose karne se pehle kaunsi properties check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Yeh hamesha 8 hai.
Ek byte mein 8 bits common hain; yeh sizeof(char) ki value nahi.
- Har implementation par sizeof(int) ke barabar hai.
Standard in dono sizes ko equal require nahi karta.
- Yeh 1 hai, C bytes mein measured.
✓ Sahi reasoning. C byte, char ka size hai. CHAR_BIT batata hai us byte mein kitni bits hain.
C17
Related ideas dekhein
09Declarations, initialization aur assignmentAbhi choice nahi
Teen ideas yaad karein
- Declaration naam ki information deti hai; kuch declarations entity define bhi karti hain.
- Initializer definition ka part hai aur later assignment expression se alag hai.
- Starting-value rules storage duration aur declaration context par depend karte hain.
const object initial value le sakta hai lekin later modification restricted kyun hoti hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Initialization initial value deti hai; baad ki assignment existing modifiable object mein value store karti hai.
✓ Sahi reasoning. Dono values se related hain, par language contexts aur rules alag ho sakte hain.
- Assignment har baar naya variable name banati hai.
Existing object ko assign karne se naya identifier introduce nahi hota.
- Har local declaration int ko zero initialize karti hai.
Initializer ke bina ordinary automatic int ko implicit zero nahi milta.
C17
Related ideas dekhein
10C ko padhna: tokens, expressions aur statementsAbhi choice nahi
Teen ideas yaad karein
- C tokens recognise karke grammar ke according combine karti hai.
- Expressions, declarations aur statements common punctuation ke bawajood different jobs karte hain.
- Whitespace tokens separate kar sakti hai; literal ke spaces data bhi ho sakte hain.
int total = count + 1; ko poora expression kahe bina uske parts kaise alag karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Expressions mein = assignment aur == equality comparison karta hai.
✓ Sahi reasoning. Unke expression roles alag hain. = token initialization syntax mein bhi aata hai; wahan woh assignment expression nahi hota.
- Whitespace decide karta hai ki dono assignment mean karte hain.
Whitespace in operators ko interchangeable nahi banata.
- Compiler programmer ke intention se meaning choose karta hai.
Language ke token aur expression rules unke roles decide karte hain.
C17
Related ideas dekhein
11Expressions aur operators: precedence se pehle meaningAbhi choice nahi
Teen ideas yaad karein
- Operand types aur conversions operation ka meaning decide karne mein help karte hain.
- Precedence aur associativity grouping describe karte hain; generally evaluation order fix nahi karte.
- Short-circuit logical operators ki specific evaluation guarantees hain; bitwise operators ka job alag hai.
&& wala guard division kaise rok sakta hai, jabki sirf parentheses evaluation order establish nahi karti?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, precedence timeline hai.
Precedence expressions group karti hai; evaluation order ke rules alag hain.
- Nahi. Grouping aur evaluation order alag rules hain.
✓ Sahi reasoning. Parentheses aur precedence expression structure batate hain; sequencing rules required order batate hain.
- Parentheses jodne se unsequenced side effects hamesha fix ho jaate hain.
Sirf grouping se sequencing introduce nahi hoti jab language use specify nahi karti.
C17
Related ideas dekhein
12Conditions, choices aur loopsAbhi choice nahi
Teen ideas yaad karein
- Conditions us point par examined state se path choose karti hain.
- Loop trace mein test, body, update aur exit dikhne chahiye.
- break, continue aur return different enclosing constructs ke rules se control transfer karte hain.
Loop zero, one ya one-too-many times chale, yeh check karne ke liye kaunsi state trace karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- while check se pehle hamesha ek baar chalta hai.
Yeh while ka rule nahi; body mein enter karne se pehle condition check hoti hai.
- Compiler har loop remove kar deta hai.
Loop behavior program semantics follow karta hai; universal removal rule nahi.
- Pehle check par controlling expression false ho sakti hai.
✓ Sahi reasoning. Initially false condition pehli body execution ko rok deti hai.
C17
Related ideas dekhein
13Functions: inputs, results aur contractsAbhi choice nahi
Teen ideas yaad karein
- Function ki declaration, definition aur call alag parts hain.
- C argument values parameters ko pass karti hai; copied pointers shared targets access kar sakte hain.
- Useful contract mein signature ke alawa ranges, effects aur failure behavior bhi hai.
Function pointer se caller ka object change kare toh bhi argument passing by value kaise rehti hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Pointer value copy hoti hai aur copy shared object refer kar sakti hai.
✓ Sahi reasoning. Function permitted pointed-to object modify kar sakta hai, par parameter alag pointer object hi hai.
- Haan, pointer parameters caller ke pointer variable ke aliases hain.
Pointer parameter value leta hai; us parameter ko assign karna caller ke pointer object ko direct assign nahi karta.
- Pointer argument poori pointed-to allocation copy karta hai.
Pointer value copy karne se referred objects copy nahi hote.
C17
Related ideas dekhein
14Recursion: alag calls ko follow kareinAbhi choice nahi
Teen ideas yaad karein
- Recursive design ko stopping case aur uski taraf justified reduction chahiye.
- Har invocation ke parameters aur ordinary automatic local instances alag hain.
- Arithmetic range, call depth aur repeated work ki limits phir bhi chahiye.
triangle(3) ko triangle(2) kyun chahiye, aur kis result se pehla waiting addition finish hota hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, branch ki presence har call ko us tak pahunchati hai.
Jo branch reach hi nahi hoti, woh recursion nahi rok sakti.
- Haan, C unlimited call depth guarantee karta hai.
Resource use aur call depth ki unlimited portable guarantees nahi hain.
- Nahi. Calls ko stopping condition ki taraf justified progress aur resource limits chahiye.
✓ Sahi reasoning. Sound reasoning valid inputs, arithmetic, depth aur repeated work bhi consider karti hai.
C17
Related ideas dekhein
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
15Comments: C mein intent samjhanaAbhi choice nahi
Teen ideas yaad karein
- Comments intent explain karte hain; ordinary executed operations nahi bante.
- Comment replacement, literals aur line splicing source interpretation affect karte hain.
- Useful comment reason ya contract batata hai aur code se consistent rehna chahiye.
Comment characters carelessly delete karne se token boundaries ya exposed source kyun badal sakte hain?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Comment whitespace se replace hota hai, jo tokens separate karta hai.
✓ Sahi reasoning. Yeh int aur count ko ek identifier mein nahi jodta.
- Comment declaration se pehle execute hota hai.
Comments translation mein handle hote hain, runtime statements ki tarah execute nahi.
- Characters identifier intcount ban jaate hain.
Comment replacement tokens concatenate karne ke bajay separation deta hai.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
16Qualifiers: read-only access aur observable effectsAbhi choice nahi
Teen ideas yaad karein
- Qualifiers declaration ke particular types aur access paths par apply hote hain.
- const access us path se modification restrict karta hai; mutable target ke saare aliases freeze nahi hote.
- volatile, restrict aur atomic facilities ke specific aur different contracts hain.
Pointer declaration mein const kis part ko qualify karta hai, yeh pehchaanne ke liye kya dekhenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Yeh access path read-only hai, par doosra permitted access original object badal sakta hai.
✓ Sahi reasoning. Isse originally const defined object modify karne ki permission nahi milti.
- Haan, har alias automatically read-only ho jaata hai.
Ek access path qualify karne se saare pointer objects aur types rewrite nahi hote.
- Pointed-to object pointer mein copy hota hai.
Pointer value object ko refer karti hai; object ki copy contain nahi karti.
C17
Related ideas dekhein
17Storage classes: duration, scope aur linkageAbhi choice nahi
Teen ideas yaad karein
- Scope, storage duration aur linkage different properties hain.
- Static-storage objects program execution tak rehte hain; thread-duration objects thread se associated hain.
- Storage-class keyword ko declaration context mein padhein; universal lifetime shortcut na banayein.
Local static object ek block execution ke baad bhi kaise rehta hai jabki naam block-scoped hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Static storage duration aur internal linkage.
✓ Sahi reasoning. Yeh object duration aur identifier linkage batati hain; naam file scope par declared hai.
- Ek function call tak limited automatic duration.
File-scope object ki ordinary automatic duration nahi hoti.
- Naam use hone par fresh dynamic allocation.
Naam refer karna nayi allocation perform nahi karta.
C17
Related ideas dekhein
18Constants, constant expressions aur compile-time checksAbhi choice nahi
Teen ideas yaad karein
- Literals, enumeration constants, read-only objects aur constant expressions alag categories hain.
- Context ko sirf unchanged runtime value ke bajaye integer constant expression chahiye ho sakta hai.
- C23 constexpr objects ke apne rules hain; C++ constexpr functions nahi milte.
Same numeric value wali do declarations different compile-time contexts mein differently accept kyun ho sakti hain?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, const har compile-time constant facility jaisa kaam karta hai.
Read-only qualification aur integer-constant-expression rules alag concepts hain.
- Nahi. Sirf const qualification woh rule satisfy nahi karti.
✓ Sahi reasoning. Relevant constant-expression context mein allowed form use karein, jaise suitable enumerator ya integer constant.
- Isse n use karne wala har array har context mein invalid hota hai.
Supported facility aur context mein nonconstant bound VLA bana sakta hai.
C17
Related ideas dekhein
19Keywords ko unke roles se samjheinAbhi choice nahi
Teen ideas yaad karein
- Keywords ko jobs se group karne par interpretation clear hota hai.
- Spelling apne role ke according declarations, control flow ya special expression rules mein aa sakti hai.
- Nayi spellings aur semantic changes ko selected C edition se jodein.
Ek keyword choose karke memorised label ke bajaye rule aur small example se uska job explain karein.
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Poore program ko hamesha turant terminate karna.
Ordinary called function se return karne par normally caller resume hota hai.
- Function body repeat karna.
return current invocation end karta hai, nayi iteration shuru nahi karta.
- Current function invocation finish karna aur required ho to value dena.
✓ Sahi reasoning. Function ka return type aur return statement value ke rules decide karte hain.
C17
Related ideas dekhein
20C keyword index: C17 aur C23Abhi choice nahi
Teen ideas yaad karein
- Yeh index corresponding theory chapters se linked lookup aid hai.
- C17 aur C23 mein keyword status aur familiar header macros alag ho sakte hain.
- Spelling pehchaanna uski constraints aur useful contexts samajhne ki shuruaat hai.
Apni C edition mein familiar spelling keyword hai ya header macro, yeh kaise check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, har standard library name keyword hai.
Library identifiers aur language keywords alag categories hain.
- Nahi. Yeh <stdio.h> se declared standard library function ka naam hai.
✓ Sahi reasoning. Header declarations deta hai; naam ko language keyword nahi banata.
- Pehli call ke baad hi keyword banta hai.
Function call se identifier ki lexical category nahi badalti.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
21Objects aur memoryAbhi choice nahi
Teen ideas yaad karein
- Objects storage occupy karte hain aur unke types, representations aur lifetimes hain.
- sizeof C bytes measure karta hai; CHAR_BIT ek C byte ke bits batata hai.
- Conceptual memory diagram relationships samjhata hai; ek physical machine layout fix nahi karta.
Object ke kaun-se facts C guarantee karti hai aur kaunsi details target implementation par check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, fixed stack layout har C object ke type ka part hai.
Type universal machine stack layout prescribe nahi karta.
- Nahi. Storage-duration aur lifetime rules woh physical arrangement mandate nahi karte.
✓ Sahi reasoning. Call stack useful common implementation model hai; uski limits batani chahiye.
- Koi local object optimize nahi ho sakta.
Implementation required program behavior preserve karte hue optimize kar sakti hai.
C17
Related ideas dekhein
Aage kahan use hota hai
22Scope, lifetime aur storage durationAbhi choice nahi
Teen ideas yaad karein
- Scope naam ki visibility aur lifetime object ke exist karne ka period hai.
- Storage duration lifetime rules deti hai; universal stack diagram nahi.
- Address rakhne se pointer target object ki lifetime extend nahi karta.
Ordinary automatic local object ka address return karne par caller ko usable target kyun nahi milta?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Object alive rehta hai, par yahan woh naam apne block scope se bahar hai.
✓ Sahi reasoning. Static storage duration aur block scope alag sawaalon ke answers hain.
- Block exit par object destroy hona zaroori hai.
Yeh ordinary automatic storage se related hai, static local ki storage duration se nahi.
- Uska naam globally visible ho jaata hai.
Static storage duration block-scope identifier ko file-scope identifier nahi banati.
C17
Related ideas dekhein
Aage kahan use hota hai
23Pointers ko samjheinAbhi choice nahi
Teen ideas yaad karein
- Pointer object pointer value store karta hai aur target se separate hai.
- Pointer copy karne se relationship copy hota hai; target copy ya lifetime extend nahi hoti.
- Valid access ko right target, lifetime, range, type aur permissions chahiye.
q ko p ki copy milne ke baad p redirect ho toh kya badlega, aur q se write karne par kya hoga?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- q automatically naye p ko follow karta hai.
Assignment ne pointer value copy ki thi, p par ongoing dependency nahi banayi.
- q apni purani pointer value rakhta hai jab tak separately change na ho.
✓ Sahi reasoning. Pointer objects alag hain, chahe unki values same target refer karein.
- Purana target automatically free ho jaata hai.
Pointer redirect karna apne aap old target ki storage release nahi karta.
C17
Related ideas dekhein
24Arrays ko samjheinAbhi choice nahi
Teen ideas yaad karein
- Array ek type ke elements ki contiguous sequence rakhta hai.
- Valid indexes existing elements identify karte hain; one-past pointer boundary hai, element nahi.
- Count aur range information available storage se consistent honi chahiye.
Element count aur largest valid index ka difference kaise explain karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- 3
Indices zero se shuru hote hain; index 3 teen elements ke bahar hai.
- Pehli stored value par depend karta hai.
Element values indexing range nahi badalti.
- 2
✓ Sahi reasoning. Element indices 0, 1 aur 2 hain.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
25Arrays aur pointers ka connectionAbhi choice nahi
Teen ideas yaad karein
- Array object aur pointer object ke types aur roles alag hain.
- Kai array expressions first element ke pointer mein convert hote hain.
- Adjusted array parameter pointer hai; uska sizeof caller ka array size recover nahi karta.
Array view receive karne wale function ko appropriate element count bhi kyun chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Use one-past bana sakte hain, par dereference nahi.
✓ Sahi reasoning. One-past permitted boundary hai; woh read karne ke liye array element designate nahi karta.
- *(a + 3) read karein kyunki pointer ban sakta hai.
Pointer banane ki permission har dereference ko valid nahi banati.
- Yeh zaroor doosre object ko point karta hai.
C us boundary par doosre usable object ki guarantee nahi deta.
C17
Related ideas dekhein
26Characters, buffers aur stringsAbhi choice nahi
Teen ideas yaad karein
- C string first null character par end hoti hai aur terminator ke liye storage chahiye.
- Capacity available storage hai; strlen valid string mein terminator se pehle units count karta hai.
- Copy ko valid regions, enough space aur operation ka overlap contract chahiye.
String function character buffer scan kare, usse pehle kaun-se facts true hone chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Capacity 3, length 6.
Yeh array element count aur first null se pehle character count ko ulta karta hai.
- Capacity 6, length 3.
✓ Sahi reasoning. Array mein chhe elements hain; strlen terminating null ko count nahi karta aur usse pehle rukta hai.
- Capacity 6, length 6.
Extra zero-initialized elements string ko first null ke aage extend nahi karte.
C17
Related ideas dekhein
27Text, Unicode, UTF-8 aur localeAbhi choice nahi
Teen ideas yaad karein
- Storage units, Unicode scalar values, grapheme clusters aur display width alag measurements hain.
- UTF-8 validation automatically normalization ya grapheme boundaries nahi deti.
- Locale-dependent C conversions ko stated state aur error rules follow karne hote hain.
Same accented letter dikhane wali do strings ka strlen different kyun ho sakta hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Yeh first null se pehle char elements count karta hai, grapheme clusters nahi.
✓ Sahi reasoning. UTF-8 code points kai bytes use kar sakte hain aur ek visible unit mein kai code points ho sakte hain.
- Haan, har visible letter exactly ek C char hai.
Yeh general Unicode ya UTF-8 guarantee nahi.
- Yeh automatically saara Unicode text decode aur normalize karta hai.
strlen terminating null dhoondhta hai; Unicode normalization operation nahi.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
28Dynamic memory aur ownershipAbhi choice nahi
Teen ideas yaad karein
- Allocation runtime par chosen size ka region request karta hai.
- Program ko size arithmetic validate, failure handle aur usable values establish karni hain.
- Ownership aur borrowing rules release aur aliases ki validity decide karte hain.
Resize fail ho toh original pointer available rakhte hue allocation replace kaise karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Purani allocation hamesha free ho chuki hoti hai.
Is positive-size failure mein old allocation deallocate nahi hoti.
- Naya teesra element use karne ke liye ready hai.
Failed growth request ne extra space nahi banayi.
- Original allocation, preserved owning pointer se reachable.
✓ Sahi reasoning. Temporary result use karein taaki failed call original allocation access aur release karne wala pointer overwrite na kare.
C17
Related ideas dekhein
29Memory mistakes ko samjheinAbhi choice nahi
Teen ideas yaad karein
- Bounds, lifetime, type aur ownership failures different memory mistakes hain.
- Non-null pointer bhi requested access ke liye invalid ho sakta hai.
- Diagnostic tools exercised cases ka evidence dete hain; sab executions ka proof nahi.
Small failing example mein buffer overrun aur use-after-free alag pehchaanne ke liye kya check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Doosre pointer objects automatically update nahi hote.
✓ Sahi reasoning. Ownership aur alias lifetimes ka contract chahiye; ek pointer clear karna sirf us pointer object ko badalta hai.
- Haan, free saare aliases dhoondhkar clear karta hai.
free allocated storage release karta hai; saare pointer objects dhoondhkar rewrite nahi karta.
- Haan, NULL wahi allocation dobara release karta hai.
NULL assign karna assignment hai, doosri deallocation operation nahi.
C17
Related ideas dekhein
Aage kahan use hota hai
30Structures: related data ka groupAbhi choice nahi
Teen ideas yaad karein
- Structure type named members describe karta hai; har structure object member values rakhta hai.
- Contained array structure ka part hai; pointer member elsewhere refer kar sakta hai.
- Member types aur relationships se meaningful record states decide hote hain.
Pointer member wale record ko referenced data ki lifetime contract kyun chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Uski poori pointed-to allocation automatically duplicate hoti hai.
Structure assignment automatic deep-copy ownership policy nahi deti.
- Pointer value copy hoti hai, isliye dono members same object refer kar sakte hain.
✓ Sahi reasoning. Ownership ya independent copy ki requirement ke liye extra contract chahiye.
- Original allocation release hoti hai.
Structure assign karna pointer members par apne aap free call nahi karta.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
31Structure values aur functionsAbhi choice nahi
Teen ideas yaad karein
- Structure copy karne par member values copy hoti hain.
- Copied pointer member do records ko same target se jod sakta hai.
- Logical comparison aur external serialization ko object-byte copy se aage policies chahiye.
Kaun-se changes sirf copied record ko aur kaun-se shared pointer target ko affect karte hain?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Copied structure ke int member ko directly naya integer assign karna.
Woh member separate parameter object ka hai.
- Copied pointer member se permitted write, jab woh ab bhi shared object refer karta ho.
✓ Sahi reasoning. Structure copy karne se pointer members ke referred objects automatically copy nahi hote.
- Koi bhi parameter change caller ki poori structure replace kar deta hai.
Structure parameter separate object hai.
C17
Related ideas dekhein
Aage kahan use hota hai
32Enumerations: choices ke naamAbhi choice nahi
Teen ideas yaad karein
- Enumeration constants choices ko meaningful names dete hain.
- Specific C17 aur C23 cases mein values aur types ke rules alag hain.
- External integers ko application ki accepted choices ke against validate karna padta hai.
File se read menu command ko named enum choice maanne se pehle check kyun karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, enum explicitly supplied values ignore karta hai.
Explicit enumerator initializers meaningful hote hain.
- Har read par value change hoti hai.
Enumerator named integer constant hai, runtime counter nahi.
- Nahi. BUSY ko explicitly 7 diya gaya hai.
✓ Sahi reasoning. Sequential defaults explicit initializer override nahi karte.
C17
Related ideas dekhein
Aage kahan use hota hai
33Unions aur tagged dataAbhi choice nahi
Teen ideas yaad karein
- Union members storage share karte hain; sabko simultaneous separate storage nahi milti.
- Tag intended interpretation identify kar sakta hai.
- Program ko tag, stored data aur allowed accesses ka relationship preserve karna hai.
Tagged union ka chosen form aur data consistent rakhne ke liye update ko kya karna chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Program, apne construction aur access contract se.
✓ Sahi reasoning. Union member assign karna separate tag field automatically update nahi karta.
- Union har separate tag automatically update karta hai.
Ordinary separate tag field ke liye C aisa automatic relationship nahi deta.
- Tag ki need nahi, kyunki har union member ki separate storage hoti hai.
Union members storage share karte hain; intended interpretation ka clear contract chahiye.
C17
Related ideas dekhein
Aage kahan use hota hai
34Records aur aggregates initialize karnaAbhi choice nahi
Teen ideas yaad karein
- Aggregate initializers type rules se members aur elements ki starting values dete hain.
- Designators selected members ya elements name karte hain; layout change nahi hota.
- Compound literals objects banate hain jinki lifetime context aur version rules par depend karti hai.
Designated initializer se record ki intended starting state reader ko clearer kyun ho sakti hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Dono mein 1 repeat hota hai.
Partial initializer last explicitly supplied value repeat nahi karta.
- Dono zero se initialize hote hain.
✓ Sahi reasoning. Baaki aggregate elements ko language ki specified implicit initialization milti hai.
- Unmein arbitrary uninitialized values hona zaroori hai.
Is aggregate ka initializer hai; omitted elements uninitialized automatic int jaise treat nahi hote.
C17
Related ideas dekhein
Aage kahan use hota hai
35Padding, alignment aur layoutAbhi choice nahi
Teen ideas yaad karein
- Alignment type ke liye suitable storage positions constrain karta hai.
- Padding se structure sizeof member sizes ke sum se bada ho sakta hai.
- Layout aur bit-field behavior ko implementation checks aur explicit external-format rules chahiye.
Poore structure bytes compare karna application ki desired equality express kyun nahi kar sakta?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, har structure mein sirf meaningful values hoti hain, padding nahi.
Implementation padding insert kar sakti hai; representations aisi general guarantee nahi deti.
- Nahi. Padding aur representations byte comparison ko value equality ke liye unsuitable bana sakti hain.
✓ Sahi reasoning. Program ki intended equality ke according meaningful members compare karein.
- memcmp hamesha member-by-member semantic comparison karta hai.
memcmp bytes compare karta hai, structure members ke meanings nahi.
C17
Related ideas dekhein
36Flexible array members ko samjheinAbhi choice nahi
Teen ideas yaad karein
- Flexible array member fixed structure members ke baad trailing elements support karta hai.
- Checked allocation arithmetic ko intended tail ke liye storage deni hai.
- Logical length, initialised payload aur actual capacity consistent honi chahiye.
Flexible-array record payload expose kare, usse pehle kaunsi calculations aur initialisations chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, array count ke according automatically grow karta hai.
Count assignment storage acquire nahi karti.
- Haan, header ka sizeof har desired payload include karta hai.
Type ka fixed size arbitrary extra payload capacity nahi deta.
- Nahi. Allocation ko separately sufficient checked capacity deni hoti hai.
✓ Sahi reasoning. Count, allocation size aur bounds consistent rakhein; allocate karne se pehle size arithmetic check karein.
C17
Related ideas dekhein
Aage kahan use hota hai
37Types, declarations aur data interfacesAbhi choice nahi
Teen ideas yaad karein
- Typedef type ko doosra naam deta hai aur pointer details hide kar sakta hai.
- Qualifiers actual aliased type par apply hote hain; declarator structure important hai.
- Useful interfaces valid states, mutation, ownership, lifetime aur failure behavior batate hain.
Pointer typedef ki wajah se const declaration ka expected meaning kaise badal sakta hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- a aur b dono.
Star, a ke declarator ka part hai; declaration ke har naam par automatically apply nahi hota.
- Sirf b.
Star, a ke declarator se attached hai.
- Sirf a; b ka type int hai.
✓ Sahi reasoning. Shared type specifier ke saath har declarator separately padhein.
C17
Related ideas dekhein
Aage kahan use hota hai
38Function pointers aur callbacksAbhi choice nahi
Teen ideas yaad karein
- Function pointer code copy kiye bina function select karta hai.
- Indirect call ko compatible function type aur called function ka contract chahiye.
- Callback ki timing, context data aur concurrency receiving API ke rules se aati hain.
Doosri operation ko callback aur data pointer dene se pehle caller ko kaunsa agreement chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Eventual call compatible function type se honi chahiye.
✓ Sahi reasoning. Cast function ka parameter aur return contract nahi badalta.
- Haan, casting function ke parameter types rewrite karti hai.
Pointer convert karna function definition rewrite nahi karta.
- Haan, har pointer type ki identical call semantics hoti hai.
Object/function pointer roles aur compatible function types phir bhi matter karte hain.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
39Preprocessing: source ki preparationAbhi choice nahi
Teen ideas yaad karein
- Preprocessing ordinary semantic analysis se pehle directives aur replacement handle karti hai.
- Preprocessor condition source select karti hai; runtime object test nahi karti.
- Configuration ke baad included source mein valid declarations aur compatible interfaces chahiye.
#if se source select karna aur ordinary if se runtime path choose karna kaise alag hain?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Dono same tarah runtime branches choose karte hain.
#if preprocessing mein handle hota hai, ordinary runtime statement ki tarah nahi.
- #if preprocessing mein source select karta hai; if ordinary execution mein path select karta hai.
✓ Sahi reasoning. Conditional inclusion batata hai kaunse source tokens later translation mein jaayenge.
- #if har runtime variable ki current value dekh sakta hai.
Preprocessing condition rules future runtime object values access nahi dete.
C17
Related ideas dekhein
40Macros: tokens, arguments aur pitfallsAbhi choice nahi
Teen ideas yaad karein
- Macros preprocessing tokens replace karte hain; functions jaise typed argument values nahi lete.
- Parentheses grouping repair kar sakti hain; repeated evaluation nahi rok sakti.
- Stringizing, token pasting aur conditional forms ke specific rules hain.
Side-effecting argument wale function-like macro ke bajaye small typed function clearer kyun ho sakta hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Macro arguments hamesha exactly ek baar evaluate hote hain.
Token substitution function-call jaisi single-evaluation guarantee nahi deta.
- Expansion expression ko ek se zyada baar evaluate kar sakti hai; sequencing bhi matter karti hai.
✓ Sahi reasoning. Replacement tokens aur sequencing inspect karein; invalid expansion ka output assume na karein.
- Parentheses har repeated side effect automatically hata deti hain.
Parentheses grouping improve kar sakti hain, duplicated evaluations nahi hataati.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
41Headers: interface share karnaAbhi choice nahi
Teen ideas yaad karein
- Headers translation ke liye interface information share karte hain.
- Guards translation unit mein repeated inclusion rok sakte hain.
- Header declarations aur linkage rules se allowed definitions ke around design hona chahiye.
Header ko independently include karne layak rakhne ke liye use kya include karna chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Header include karna hamesha library link karta hai.
Header inclusion aur compiled definitions supply karna alag build concerns hain.
- Header alag running program hai.
Headers inclusion se source dete hain; independent programs ki tarah run nahi hote.
- Translation units ke beech consistent interface share karne ke liye.
✓ Sahi reasoning. Declarations functions ke uses aur definitions check karne wali files mein include ho sakti hain.
C17
Related ideas dekhein
42Translation units aur linkageAbhi choice nahi
Teen ideas yaad karein
- Har translation unit ka apna preprocessing aur declaration context hai.
- Linkage appropriate contexts ki same-entity declarations connect karti hai.
- Shared interfaces ko compatible declarations aur correct program-level definitions chahiye.
Do files translate hokar bhi shared entity ke interface par disagree kaise kar sakti hain?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Unke identifiers ki apni translation units mein internal linkage hai.
✓ Sahi reasoning. Same spelling, internal-linkage identifiers ki shared external identity establish nahi karti.
- Haan, har matching spelling ek global object name karti hai.
Scope aur linkage rules matter karte hain; sirf matching text enough nahi.
- static ka matlab hamesha block scope hai.
static file-scope declarations mein bhi ho sakta hai; scope declaration location par depend karta hai.
C17
Related ideas dekhein
Aage kahan use hota hai
43Linking aur librariesAbhi choice nahi
Teen ideas yaad karein
- Linking references ko build mein supplied definitions se connect karti hai.
- Static archives aur shared libraries toolchain rules se components package karti hain.
- Compatible naam akela full ABI aur ownership contract establish nahi karta.
Missing definition, incompatible declaration aur unavailable shared dependency ko kaun-sa evidence alag karega?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Declaration type checking mein help karti hai; build ko required implementation phir bhi chahiye.
✓ Sahi reasoning. Toolchain library definitions kaise supply karti hai, yeh header inclusion se alag hai.
- Header include karna computer ki har library build karta hai.
Header inclusion source declarations deta hai, universal library-build operation nahi.
- Har C implementation same library command-line flags require karti hai.
Toolchain flags implementation-specific interfaces hain.
C17
Related ideas dekhein
44Standard library: facilities aur contractsAbhi choice nahi
Teen ideas yaad karein
- Library facilities supported jobs ke hisaab se organised hain.
- Har call ke argument, storage, result aur failure rules hain.
- Hosted, freestanding, optional aur platform facilities ki availability contracts alag hain.
Pointer aur count dene se pehle library function ki documentation mein kya check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, library saare invalid pointers repair karti hai.
Library interface caller ki pointer aur lifetime obligations nahi hataata.
- Haan, header successful resource acquisition guarantee karta hai.
Allocation aur file opening jaise operations phir bhi fail ho sakte hain.
- Nahi. Caller ko function ke argument aur state contracts bhi satisfy karne hote hain.
✓ Sahi reasoning. Bounds, formats, lifetimes aur error handling correct use ka part rehte hain.
C17
Related ideas dekhein
Pehle ke ideas
45Modular programs: contracts aur buildsAbhi choice nahi
Teen ideas yaad karein
- Module ki coherent responsibility aur clear interface honi chahiye.
- Private representation aur helpers se doosre code ko kam state samajhni padti hai.
- Build dependencies mein implementation files ke saath shared interface changes bhi aane chahiye.
Doosre programmer ko module ke accepted inputs aur rejection par unchanged policy kaise describe karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Interface header include karna saari definitions automatically supply karta hai.
Header declarations function bodies automatically link nahi karti.
- Caller ko function ka type guess karna chahiye.
Interface check karne ke liye consistent declaration chahiye.
- Header se declarations share karein aur implementation source build mein dein.
✓ Sahi reasoning. Build ko program ki required definitions translate aur connect karni hoti hain.
C17
Related ideas dekhein
46Arguments, conversion aur environmentAbhi choice nahi
Teen ideas yaad karein
- Command-line arguments hosted startup interface se aayi strings hain.
- Number parse karna aur application value accept karna alag checks hain.
- Borrowed environment strings ke availability aur invalidation rules hain.
Ek command-line argument ko zero se 100 level accept karne se pehle kya check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, argv numeric-looking text automatically convert karta hai.
argv strings deta hai; numeric validation nahi karta.
- Nahi. Parse karke accepted syntax aur range check karein.
✓ Sahi reasoning. Presence, conversion success aur acceptable value range alag checks hain.
- Haan, argc har argument ki numeric value record karta hai.
argc arguments count karta hai; unka numeric content nahi batata.
C17
Related ideas dekhein
47Variadic functions: arguments ka agreementAbhi choice nahi
Teen ideas yaad karein
- Trailing variadic arguments ke count aur types ka explicit agreement chahiye.
- Default promotions va_arg ke retrieval type ko affect karti hain.
- Har va_start ya va_copy traversal ka corresponding va_end chahiye.
Ellipsis ke baad passed float ko double ke roop mein retrieve kyun karna hota hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- float, bina change.
Ellipsis se corresponding arguments par default argument promotions apply hoti hain.
- double.
✓ Sahi reasoning. Receiving variadic code ko promoted-type agreement follow karna chahiye; ise float ke roop mein retrieve na karein.
- Caller ke float object ka pointer.
Yeh value conversion hai, implicit address-taking operation nahi.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
48Comparison rule se searching aur sortingAbhi choice nahi
Teen ideas yaad karein
- Comparator result ke sign se consistent ordering deta hai.
- qsort equal elements reorder kar sakta hai aur particular algorithm promise nahi karta.
- bsearch ko required key-relative arrangement chahiye aur koi bhi equal match mil sakta hai.
Array sort karne aur comparison callback se search karne ke beech kya consistent rehna chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Comparator ko hamesha exactly 1 return karna chahiye.
Comparison rule ko required signs se less, equal aur greater distinguish karna hota hai.
- Saare subtraction results automatically Boolean hain.
Ordinary integer subtraction zero aur one tak restricted nahi.
- Signed subtraction overflow karke valid ordering express karne mein fail ho sakti hai.
✓ Sahi reasoning. Potentially overflowing difference ke bajay safe comparisons aur consistent ordering contract use karein.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
49Streams, buffering aur EOFAbhi choice nahi
Teen ideas yaad karein
- 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.
Character read ko char mein narrow karne se pehle int mein store aur check kyun karenge?
Is idea ki reasoning 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
Related ideas dekhein
Aage kahan use hota hai
50Formatted output aur format contractsAbhi choice nahi
Teen ideas yaad karein
- Formats supplied argument types aur relevant promotions se match hone chahiye.
- Width, precision aur destination capacity different formatting questions hain.
- Output errors aur truncation ko chosen function ke rules se check karna hai.
snprintf ke baad buffer ko complete requested message maanne se pehle kya check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Sirf output kitne characters jaisa dikhna chahiye.
Appearance se conversion ka valid argument type establish nahi hota.
- Sirf variable ke naam se.
Identifier spelling argument ka required type nahi batati.
- Applicable argument promotions ke baad actual argument type se.
✓ Sahi reasoning. Format string contract hai; woh mismatched argument ko generally required type mein convert nahi karti.
C17
Related ideas dekhein
Aage kahan use hota hai
51Formatted input: matching aur limitsAbhi choice nahi
Teen ideas yaad karein
- 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.
First conversion ki success se poora requested input record accept hona kyun establish nahi hota?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- 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.
- scanf pehle har destination zero kar deta hai.
Failed conversion destination ko zero initialize karne ka promise nahi karti.
- Width limit valid numeric range guarantee karti hai.
Field width consumed input limit karti hai; yeh general numeric-range validation strategy nahi.
C17
Related ideas dekhein
Aage kahan use hota hai
52Lines, boundaries aur checked parsingAbhi choice nahi
Teen ideas yaad karein
- Complete input record aur input call ke returned chunks alag hain.
- Parsing mein valid data, incomplete input, invalid text aur out-of-range values alag karein.
- Required checks successful hone ke baad accepted value commit karein.
Overlong line reject karke next input record ko read ke liye ready kaise rakhenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, terminating null prove karta hai ki poori line fit hui.
Null termination prove nahi karti ki newline ya poori logical line consume hui.
- Haan, buffer size automatically grow hota hai.
fgets supplied buffer dynamically enlarge nahi karta.
- Nahi. Line end hone se pehle buffer fill ho sakta hai.
✓ Sahi reasoning. Input policy ke according incomplete lines detect aur handle karein.
C17
Related ideas dekhein
53Files open karna, modes aur lifetimesAbhi choice nahi
Teen ideas yaad karein
- Opening mode reading, creation, replacement, append ya update behavior choose karta hai.
- Opening later write se pehle file modify ya fail kar sakti hai.
- Stream ownership mein appropriate close aur uski possible failure shamil hai.
Naya destination create karte waqt existing file protect karne ke liye kaunsa mode aur failure policy choose karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Returned pointer NULL hai ya nahi.
✓ Sahi reasoning. NULL open karne ki failure batata hai; use valid stream maankar use karna contract violate karega.
- Returned pointer EOF ke barabar hai ya nahi.
EOF doosre I/O interfaces ka integer macro hai, fopen ka failure pointer nahi.
- Sirf filename mein dot hai ya nahi.
Filename ka appearance opening successful hone ka proof nahi.
C17
Related ideas dekhein
Aage kahan use hota hai
54Block I/O, positions aur update streamsAbhi choice nahi
Teen ideas yaad karein
- Block I/O complete transferred elements report karta hai; poori request ki success promise nahi karta.
- Position tokens aur text offsets ke specific stream rules hain.
- Update streams mein reading-writing ke correct transitions chahiye.
Short block read ke baad final record ya error decide karne se pehle kya inspect karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Successfully written elements ki count.
✓ Sahi reasoning. Result elements count karta hai. Element size ek byte ho to yeh seedha byte count bhi deta hai.
- Hamesha total requested bytes ki count.
Result completed elements batata hai aur short ho sakta hai.
- Guarantee ki later flush ya close fail nahi ho sakta.
Buffered output mein later errors aa sakte hain; yahan ki success woh broader guarantee nahi.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
55Errors, status, errno aur assertionsAbhi choice nahi
Teen ideas yaad karein
- Interfaces documented status aur result conventions se failure report karti hain.
- errno applicable operation ke error rules ke under hi meaningful hai.
- Assertions assumptions express karti hain; har build ki required validation replace nahi karti.
Unrelated successful operation ke baad nonzero errno new failure ka enough evidence kyun nahi hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, har successful function errno reset karta hai.
Successful functions generally errno clear karne ka promise nahi karti.
- Haan, errno har function ki return value replace karta hai.
Har interface apna error indication aur errno kab meaningful hai, define karta hai.
- Nahi. Us function ke documented failure indication aur errno rules follow karein.
✓ Sahi reasoning. Value kisi earlier operation se bachi ho sakti hai.
C17
Related ideas dekhein
56Ownership, cleanup aur partial workAbhi choice nahi
Teen ideas yaad karein
- Cleanup depend karti hai ki failure se pehle kaun-se resources acquire hue.
- Ownership release ki responsibility aur references ki validity batati hai.
- Resources close karne se external partial work undo ya durable storage prove nahi hota.
File copy beech mein fail ho toh kaun-se resources aur partial effects track karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Har imagined resource release karein, jo acquired hi nahi hua use bhi.
Cleanup actual acquisition state aur API contract follow kare.
- Turant return karein aur pehle resource ka owner koi na rahe.
Ownership kho dene se pehla resource leak ho sakta hai.
- Ownership contract ke according pehla resource release ya transfer karein.
✓ Sahi reasoning. Partial work mein bhi already acquired resources ki cleanup obligations hoti hain.
C17
Related ideas dekhein
57Dates, clocks aur time measurementAbhi choice nahi
Teen ideas yaad karein
- Calendar time, elapsed duration aur processor time alag questions ke answers hain.
- Calendar fields, conversions aur formatting ke conventions aur failure cases hain.
- Clock availability, resolution, range aur monotonicity separately check karein.
Two seconds wait karne wala program bahut kam processor time kyun use kar sakta hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Hamesha calendar date, Unix seconds mein.
Calendar time aur time_t representation, clock ke interface se alag hain.
- Program ka used processor time, general wall-clock stopwatch nahi.
✓ Sahi reasoning. Interface ki limits ke saath availability check karein aur CLOCKS_PER_SEC se conversion karein.
- Executed source lines ki count.
Yeh clock interface source-line count report nahi karta.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
58Behavior, guarantees aur undefined behaviorAbhi choice nahi
Teen ideas yaad karein
- Undefined, unspecified aur implementation-defined behavior different language categories hain.
- Language-valid operation application requirements tod sakta hai.
- Ek observed result language ki absent guarantee establish nahi karta.
Do observed outputs allowed choice hain ya invalid operation, yeh kaise decide karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Ki operation portable hai.
Ek observed outcome language guarantee nahi bana sakta.
- Sirf ki is run mein yeh observation mila.
✓ Sahi reasoning. Undefined behavior ke liye C standard requirements impose nahi karta; sahi dikhta run operation validate nahi karta.
- Ki compiler ko har baar warning deni hogi.
Har possible undefined behavior ke liye diagnostic required nahi.
C17
Related ideas dekhein
59Evaluation order aur side effectsAbhi choice nahi
Teen ideas yaad karein
- Value computations aur side effects ka order expression grouping se aage rules follow karta hai.
- Specific operators aur full-expression boundaries sequencing guarantees dete hain.
- Unsequenced conflicting accesses sirf multiple results ke bajaye undefined behavior de sakte hain.
Do operations ka order required ho toh separate statements use kaise clearer banati hain?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Dono operands hamesha kisi bhi order mein chalte hain.
Right operand conditionally evaluate hota hai, left ke baad.
- Left operand pehle evaluate hota hai; right sirf left nonzero ho tab evaluate hota hai.
✓ Sahi reasoning. Logical-AND operator short-circuit evaluation aur sequencing deta hai.
- Right operand hamesha pehle chalta hai.
Yeh is operator ka required evaluation relationship ulta karta hai.
C17
Related ideas dekhein
Aage kahan use hota hai
60Effective types, aliases aur accessAbhi choice nahi
Teen ideas yaad karein
- Typed access object, lifetime, alignment aur allowed access type par depend karta hai.
- Character representation view arbitrary typed reinterpretation allow nahi karta.
- restrict relevant accesses ka contract hai; sirf pointers different hone ka synonym nahi.
Enough bytes wala buffer converted typed pointer ke access ke liye phir bhi unsuitable kyun ho sakta hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Cast automatically destination type ka naya object bana deta hai.
Pointer ka type badalna generally naya pointed-to object create nahi karta.
- Cast har possible access type valid bana deta hai.
Language restrict karti hai ki kaunse types object ki stored value access kar sakte hain.
- Lifetime, access-type rules aur bounds ko bhi operation permit karna chahiye.
✓ Sahi reasoning. Character-type representation access arbitrary typed reads ki unrestricted permission nahi deta.
C17
Related ideas dekhein
61Portability aur explicit assumptionsAbhi choice nahi
Teen ideas yaad karein
- Portable design mein pehle required target properties batate hain.
- Language guarantees aur implementation-specific choices alag rakhni hain.
- Explicit conversions, width checks aur format definitions assumptions reviewable banate hain.
Do machines ke beech two-octet numeric format share karne se pehle kaun-si assumptions document karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Suitable type available hone par implementation exact-width typedef deti hai.
✓ Sahi reasoning. Implementation ki facilities check kiye bina optional exact-width type assume na karein.
- Haan, int ka exactly 32-bit hona required hai.
C17 universal 32-bit int require nahi karta.
- Haan, koi bhi header include karne se saari integer widths ban jaati hain.
Header unsupported integer representation create nahi kar sakta.
C17
Related ideas dekhein
62Floating-point calculations aur math functionsAbhi choice nahi
Teen ideas yaad karein
- Floating-point values ki range aur precision finite hain; rounding implementation rules follow karti hai.
- Comparison tolerance application units, domain aur acceptable error se aati hai.
- Math domains, special values aur error reporting ki explicit policies chahiye.
Addition order se floating-point observation badle toh compiler wrong hona kyun prove nahi hota?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, exceptions aur math_errhandling kabhi matter nahi karte.
Implementation ki advertised error-handling facilities matter karti hain.
- Haan, har finite result prove karta hai ki domain ya range issue nahi tha.
Is general shortcut ke bajay relevant function aur error contract inspect karein.
- Nahi. math_errhandling aur relevant function ke result/error rules follow karein.
✓ Sahi reasoning. Applicable errno aur floating-point exception reporting implementation contract ke according handle karein.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
63Defensive C aur security boundariesAbhi choice nahi
Teen ideas yaad karein
- Validation mein semantic domains, resource limits aur checked size arithmetic hain.
- Pointer aur count contracts ko genuinely accessible regions phir bhi chahiye.
- Defensive choices clear threat aur ownership model ke under specified risks reduce karti hain.
Input-controlled element count ka space calculate aur allocate karne se pehle kya check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Claimed length ko capacity check kiye bina trust karein.
Supplied length bhi input hai; woh receiving buffer ki bounds violate kar sakti hai.
- Operation safe banane ke liye buffer rename karein.
Names intent communicate karte hain, valid copy enforce nahi karte.
- Copy contract ke liye length, capacity aur required arithmetic validate karein.
✓ Sahi reasoning. C string required ho to contract mein terminator ki space bhi account karein.
C17
Related ideas dekhein
64External data formats: bytes ka agreementAbhi choice nahi
Teen ideas yaad karein
- External format fields aur encodings ko raw structure layout se independently define karta hai.
- Width, octet order, version aur length reader-writer agreement ke rules hain.
- Result commit se pehle complete record validate aur partial input explicitly handle karein.
Encoder-decoder round trip ke alawa exact expected-byte test useful kyun hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Layout, padding, byte order aur representations ka explicit format agreement phir bhi chahiye.
✓ Sahi reasoning. Fields aur encoding define karke unhe deliberately serialize aur validate karein.
- Haan, binary mode har structure ka layout standardize karta hai.
Binary mode universal structure representation impose nahi karta.
- Haan, sirf sizeof poora external protocol describe karta hai.
Local byte size bytes ke meanings ya encoding specify nahi karta.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
65Threads, atomics aur shared stateAbhi choice nahi
Teen ideas yaad karein
- Shared mutable state ko required access aur ordering rules chahiye.
- Atomic operations larger multi-step update ko automatically transaction nahi banate.
- Synchronization, resource lifetimes aur API support design se match hone chahiye.
Flag publish karne par uske associated ordinary data ke liye ordering agreement kyun chahiye?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, volatile thread lock hai.
volatile mutex nahi aur apne aap atomicity ya synchronization nahi deta.
- Nahi. Suitable synchronization ya atomic-access design phir bhi chahiye.
✓ Sahi reasoning. Conflicting unsynchronized non-atomic accesses data race bana sakte hain.
- Har access indivisible operation ban jaata hai.
volatile generally ordinary operations ko atomic operations nahi banata.
C17
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
66Diagnostics, debugging aur evidenceAbhi choice nahi
Teen ideas yaad karein
- Useful bug report failure reproduce karwati hai aur expected behavior batati hai.
- Diagnostics, debugger observations aur sanitizers different questions ke answers dete hain.
- Regression check failure wali boundary ya assumption exercise kare.
Compiler options ya input guess kiye bina doosre ko failure investigate karne ke liye kya evidence denge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Exercised executions mein covered problem report nahi hui.
✓ Sahi reasoning. Yeh useful evidence hai, par har input, path ya tool limitation ke liye proof nahi.
- Har possible execution valid C hai.
Finite test run har possible execution explore nahi karta.
- Implementation ko ab language rules ki need nahi.
Tools language rules ko support karte hain; replace nahi.
General
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
67Style, contracts aur code reviewAbhi choice nahi
Teen ideas yaad karein
- Readable names aur interfaces se assumptions inspect karna aasaan hota hai.
- Validation aur state updates ka deliberate reviewable order hona chahiye.
- Style guidelines language rules aur application contract ko complement karti hain.
Kaunsa naming ya control-flow change function ka rejection path review karna easier banayega?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Haan, formatting resources automatically release karti hai.
Formatting runtime cleanup nahi karti.
- Nahi. Woh contract communicate karte hain, par use design aur follow karna phir bhi zaroori hai.
✓ Sahi reasoning. Readable code reasoning aasaan karta hai; har operation automatically correct nahi banata.
- Haan, descriptive pointer name uski lifetime prove karta hai.
Naam object ke abhi alive hone ka evidence nahi.
General
Related ideas dekhein
Aage kahan use hota hai
68C ki timeline: history, editions aur standardsAbhi choice nahi
Teen ideas yaad karein
- C ki published editions aur working drafts ka status alag hai.
- C23 jaisa nickname ISO publication year se different ho sakta hai.
- Older resource ko intended edition aur current implementation support ke context mein padhein.
Older book ya compiler preview feature use karne se pehle kaunsi dates aur version claims check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Har purana convention modern C mein required hai.
Historical practice aur current language requirement alag hain.
- Editions ke beech rules aur available features alag ho sakte hain.
✓ Sahi reasoning. Example ko portable rule maanne se pehle edition aur assumptions check karein.
- Sirf publication date compiler support prove karti hai.
Implementation support standard ki publication se separately check karna hota hai.
General
Related ideas dekhein
Pehle ke ideas
Aage kahan use hota hai
69C aisi kyun hai: design aur tradeoffsAbhi choice nahi
Teen ideas yaad karein
- C features practical systems needs ko explicit language contracts se jodte hain.
- Efficiency aur portability program choices aur implementation conditions par depend karti hain.
- Tradeoff samajhna compact syntax ko complete explanation maanne se zyada useful hai.
Ek C feature choose karke uski solved problem aur programmer ki remaining responsibility explain karein.
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Har invalid access runtime par automatically reject hota hai.
C har invalid operation ke liye runtime check promise nahi karta.
- Pointer syntax se bounds jaanne ki need khatam hoti hai.
Pointer value generally complete bounds contract carry nahi karti.
- Program ko bounds, lifetimes aur operation contracts follow karne hote hain.
✓ Sahi reasoning. Direct control tab useful hai jab program valid operations ki required conditions bhi maintain kare.
C17
Related ideas dekhein
70C ka influence: languages, runtimes aur interfacesAbhi choice nahi
Teen ideas yaad karein
- Historical influence, similar syntax, implementation language aur foreign interfaces different relationships hain.
- C mein written runtime apni language ko C semantics nahi deta.
- Language boundary par compatible ABI, ownership aur lifetime contracts chahiye.
Doosri language C par based hai kehne ka kaun-kaun sa different meaning ho sakta hai?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Nahi. Us language ke apne type, lifetime aur operation rules seekhein.
✓ Sahi reasoning. Syntax influence identical behavior establish nahi karta.
- Haan, matching braces ka matlab matching memory rules hai.
Sirf braces poori language ka memory model define nahi karti.
- Haan, C se influenced har language mein har C feature hota hai.
Influence selected ideas ka ho sakta hai, poori language ka nahi.
General
Related ideas dekhein
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
71Modern C: C23 features aur adoptionAbhi choice nahi
Teen ideas yaad karein
- C23 apne contracts ke saath language aur library features add karta hai.
- Compiler support, library support aur target availability alag checks hain.
- Nayi syntax bounds, lifetime, range ya argument-type requirements remove nahi karti.
Several toolchains wale program mein C23 facility use karne se pehle use kaise verify karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Sirf source file .c par end hoti hai.
Extension se na language edition establish hoti hai na feature support.
- Ki ek unrelated C23 example compile hua.
Ek feature ka support har language aur library change ka support prove nahi karta.
- Selected language mode aur us feature ka actual compiler/library support.
✓ Sahi reasoning. Language edition aur implementation support alag hain. Documented support aur relevant feature check use karein.
C23 adoption
Related ideas dekhein
72Complete programs ko contracts se samjheinAbhi choice nahi
Teen ideas yaad karein
- Complete program kai object, control-flow aur interface contracts jodta hai.
- Success, rejection aur cleanup paths sab promised behavior ka part hain.
- Boundary cases reasoning test karte hain; har possible execution prove nahi karte.
Ek complete example choose karke batayein ki invalid input reject hone par kya unchanged rehta hai.
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Uski input assumptions, boundaries, failures aur resource handling.
✓ Sahi reasoning. Observed output bade contract ke baare mein evidence ka ek part hai.
- Sirf variable names doosre example se match karte hain ya nahi.
Sirf names equivalent behavior establish nahi karte.
- Kuch nahi; ek output har execution prove karta hai.
Different inputs aur paths different conditions exercise kar sakte hain.
General
Related ideas dekhein
73Model ko aage le jaayein: review aur next stepsAbhi choice nahi
Teen ideas yaad karein
- Reading path ko concepts jodne wala map samjhein; one-time checklist nahi.
- Observed result generalise karne se pehle rule, preconditions aur boundary explain karein.
- Practice, reproducible questions aur feedback se missing explanation steps milte hain.
Kaunsa idea ab zyada precisely explain kar sakte hain, aur new program mein kaunsi assumption check karenge?
Is idea ki reasoning check karein
Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.
Har choice ki explanation padhein
- Validity conditions ke bina sirf syntax repeat karein.
Conditions samajhne ka part hain ki operation kab use ho sakta hai.
- Batayein kya karta hai, kyun useful hai aur kaunsi conditions use valid rakhti hain.
✓ Sahi reasoning. Meaning, purpose aur limits ko jodna memorized example ke aage reasoning mein help karta hai.
- Assume karein compiler har mistake rok dega.
Compiler diagnostics har invalid operation ya incorrect intention cover nahi karti.
General
Related ideas dekhein
Aage kahan use hota hai
Yeh topic is learning path ka ek review ya deeper endpoint hai.
Apni revision choices ki copy rakhein
Yahan se revision choices export ya restore karein. Notebook aur reading-preferences backup Reading settings mein available rehta hai. Import newer choices merge karta hai; existing newer choices preserve hoti hain.