Enumerations: choices ke naam
States ko clear names dein; enum types, numeric representations, accepted inputs aur C23 extensions alag rakhein.
Is chapter mein8 sections
Unexplained numbers ke bajaye named choices code ko clear banati hain. Enumeration names aur values deti hai, lekin bahar se aaye har integer ko validate nahi karti. Names, type rules aur application ke valid states alag samjhenge.
1. Choices ko names dein
Enumeration enumerated type aur named enumeration constants define karti hai. Is C17 example mein first implicit value zero hai, explicit value sequence ka new point set karti hai aur next implicit value one add karti hai. Resulting values ko C17 ki representability requirements satisfy karni hoti hain.
enum State {
STATE_READY,
STATE_RUNNING = 4,
STATE_DONE
};
enum State current = STATE_READY;
current = STATE_DONE;
- STATE_READY
- 0
- STATE_RUNNING
- 4
- STATE_DONE
- 5
STATE_DONE assign karna label print nahi karta aur pehle STATE_RUNNING se pass hona require nahi karta. State machine ko additional transition rules chahiye. Enumeration names aur type deti hai; interface allowed states aur transitions define karta hai.
2. C17 constants aur enum objects ke types alag samjhein
C17 mein enumeration constants ka type int hai aur defining values int mein representable honi chahiye. Enumerated type khud implementation-chosen char, signed integer ya unsigned integer type ke compatible hota hai jo members represent kar sake. Sirf enum spelling se byte size ya signedness infer na karein.
Enumeration constants ordinary identifiers hain, C++ ke State::READY jaise scoped names nahi. STATE_ prefixes shared scopes mein collisions avoid karne mein help karte hain. Integer promotions aur conversions ho sakti hain; enum declaration runtime membership test nahi.
3. External values accept karne se pehle validate karein
#include <assert.h>
#include <stdbool.h>
#include <stddef.h>
enum State { STATE_READY, STATE_RUNNING, STATE_DONE };
static bool state_from_int(int input, enum State *result)
{
if (result == NULL) return false;
switch (input) {
case STATE_READY: *result = STATE_READY; return true;
case STATE_RUNNING: *result = STATE_RUNNING; return true;
case STATE_DONE: *result = STATE_DONE; return true;
default: return false;
}
}
int main(void)
{
enum State current = STATE_READY;
assert(!state_from_int(99, ¤t));
assert(current == STATE_READY);
assert(state_from_int(STATE_DONE, ¤t));
assert(current == STATE_DONE);
return 0;
}
Function sirf explicitly recognized choices accept karta hai. Invalid input caller ka object unchanged rakhta hai. Yeh program ka chosen contract hai, enum type ka naam dene ka automatic effect nahi. Incoming integer check karne se enum conversion ko network field, file value ya user input ki validation samajhne ki mistake avoid hoti hai.
switch mein default branch unrecognized values handle kar sakti hai. C generally har named enumerator ko switch mein cover karna require nahi karti. Compiler warnings missing cases notice karne mein help kar sakti hain, lekin data contract ko unexpected input aur new states ka behavior define karna hoga.
4. Different names ki values equal ho sakti hain
enum Result { RESULT_OK = 0, RESULT_SUCCESS = 0, RESULT_ERROR = 1 };
enum Result status = RESULT_SUCCESS;
Explicit enumerators same value share kar sakte hain. Yeh compatibility alias express kar sakta hai, lekin runtime integer value original spelling nahi bata sakti. Ek switch mein same converted value wale do case labels allowed nahi. Alternatives distinguish karne hon toh distinct values choose karein.
5. C23 enum model expand karta hai
Fixed underlying type deliberate interface choice mein help karta hai. Woh file format ka byte order define nahi karta, arbitrary external integer validate nahi karta aur C++ scoped-enum semantics add nahi karta. Representation choices, accepted values aur transition rules alag decisions rakhein.
Primary references aur aage padhne ke liye
- WG14 N1570 — public C11 committee draft: 6.7.2.2, 6.3.1.1, 6.8.4.2. C17 baseline ke stable core rules; yeh final ISO publication nahi hai.
- WG14 N3096 — public C23 working draft: 6.7.2.2p11–p15. C23 notes, C17 example checks se separate hain.
Aage badhne se pehle
- 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.
In ideas ko alag rakhein
- Enum representation / Valid application state
- Representable ya convertible integer khud se accepted application state establish nahi karta.
File se read menu command ko named enum choice maanne se pehle 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
- 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
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.