Evaluation order aur side effects
Full expressions, short-circuit guards, comma operators, function calls aur unsequenced conflicts trace karein.
Is chapter mein8 sections
Expression ka grouping pata hone se hamesha evaluation order nahi pata chalta. Sequencing rules C ke required ordering relationships batate hain. Inse flexible order aur conflicting invalid accesses ka difference samjhenge.
1. Value computation aur side effects separate karein
Side effect execution state change karta hai, jaise object modification ya I/O. Value computation value obtain ya object identify karti hai. Post-increment old value produce karke object bhi modify karta hai; pre-increment updated value produce karta hai. Is description se surrounding expression par universal operator priority nahi milti.
int value = 1;
int before = value++;
int after = ++value;
Yahan initializers separate full expressions hain. Ek full expression ki evaluations aur side effects next evaluated full expression se sequenced before hoti hain. First increment later initializer ke use se pehle complete hai. Dependent updates separate statements mein rakhna required order express karne ka often clearest tareeka hai.
2. Teen ordering relationships samjhein
| Relationship | Meaning |
|---|---|
| Sequenced before | Specified relation mein A, B begin hone se pehle finish hota hai. |
| Indeterminately sequenced | A pehle ya B pehle, without interleaving; chosen order unspecified. |
| Unsequenced | Koi evaluation doosri se sequenced before nahi; order infer na karein. |
Precedence aur associativity expression grouping batati hain. Parentheses grouping clarify karti hain; khud sequencing create nahi karti. Additions group karne se generally operands ka evaluation order decide nahi hota. Sequencing rule language construct ya explicit program step se aayegi.
3. Actual sequencing establish karne wale constructs use karein
int divisor = 0;
bool accepted = divisor != 0 && 12 / divisor > 2;
Logical && aur || mein left operand pehle evaluate aur right sirf needed ho tab evaluate hota hai. ?: ka first operand selected branch se pehle evaluate aur sirf one branch selected hoti hai. Guard later division ya pointer access protect kar sakta hai, jab guard aur remaining preconditions valid hon.
int value = 0;
int result = (value = 3, value + 2);
Comma operator left operand ko right se pehle sequence aur right ka value produce karta hai. Function arguments ya declarations separate karne wala comma different syntax hai aur general ordering guarantee nahi deta. Yahan parentheses comma-operator expression select karti hain, declaration separator nahi.
4. Unsequenced conflicts ka valid output predict nahi kar sakte
C17 mein f(i++, i++) same scalar object ki unsequenced modifications hai. i++ + i bhi unsequenced modification aur us object ki value computation combine karta hai. Yeh undefined behavior hain. ++ ko longer assignment se replace ya parentheses add karna automatically fix nahi. Intended argument values earlier explicit steps mein compute karein.
5. Function executions aur argument evaluations distinct hain
#include <assert.h>
#include <string.h>
static char trace[3];
static unsigned used;
static int left(void) { trace[used++] = 'L'; return 1; }
static int right(void) { trace[used++] = 'R'; return 2; }
static int add(int first, int second) { return first + second; }
int main(void)
{
int sum = add(left(), right());
trace[used] = '\0';
assert(sum == 3 && used == 2);
assert(strcmp(trace, "LR") == 0 || strcmp(trace, "RL") == 0);
return 0;
}
Example mein left aur right separate function executions hain jinke bodies C17 sequencing rule ke under interleave nahi hote. Order unspecified hai, isliye dono traces accepted; add ko completed results milte hain. Isse two i++ jaisi arbitrary argument expressions safe nahi hoti. Function bodies, argument computations aur eventual call evaluation model ke different parts hain.
Primary references aur aage ki reading
- WG14 N1570 — public C11 committee draft: 5.1.2.3, 6.5p2–p3, 6.5.2.2p10, 6.5.13–6.5.15, 6.5.17, 6.8p4. C17 baseline ke stable core rules ke liye; final ISO publication nahi.
- WG14 N3096 — public C23 working draft: 6.5, 6.5.2.2. C23 notes C17 example checks se separately source-reviewed hain.
Aage badhne se pehle
- 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.
In ideas ko alag rakhein
- Associativity / Evaluation order
- Associativity related precedence ke operators group karti hai; generally runtime operand order prescribe nahi karti.
Do operations ka order required ho toh separate statements use kaise clearer banati hain?
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
- 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
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.