Unions aur tagged data
Alternatives ke liye shared storage use karein aur explicit tag ko selected payload se jodne wala contract maintain karein.
Is chapter mein8 sections
Kabhi value kai possible forms mein se ek form le sakti hai. Union un forms ko storage share karne deta hai. Alag tag intended form record kar sakta hai, lekin tag aur data ko consistent rakhna program ki responsibility hai.
1. Alternatives ek storage region share karte hain
Union largest member ke liye sufficiently large hoti hai aur padding include kar sakti hai. Members overlap karte hain; structure ke members jaise independent slots nahi. ratio write karna later retrieval ke liye separate count value preserve nahi karta. Example doosri representation select karne se pehle count ko alag object mein save karta hai.
union Number { int count; double ratio; };
union Number value = {.count = 7};
int count = value.count;
value.ratio = 0.5;
double ratio = value.ratio;
Ek workspace imagine karein jo multiple jobs mein se ek ke liye arrange hai. Analogy ki limit: C workspace par automatic label nahi lagati jo future code ko selected job bataye. Raw union value shared storage deti hai, self-checking variant nahi.
2. Tag program ki interpretation record karta hai
#include <assert.h>
enum ReadingKind { READING_COUNT, READING_RATIO };
struct Reading {
enum ReadingKind kind;
union { int count; double ratio; } data;
};
static int count_or_zero(const struct Reading *reading)
{
if (reading->kind == READING_COUNT) return reading->data.count;
return 0;
}
int main(void)
{
struct Reading item = {.kind = READING_COUNT, .data = {.count = 7}};
assert(count_or_zero(&item) == 7);
item = (struct Reading){.kind = READING_RATIO, .data = {.ratio = 0.5}};
assert(count_or_zero(&item) == 0);
return 0;
}
- kind
- READING_COUNT
- shared payload
- data.count = 7
Tag ya discriminant enclosing structure ka part hai. Contract ke according count tag count member read karne deta hai; ratio tag ratio member select karta hai. Saare constructors, updates, copies aur readers ko invariant follow karna hoga. Sirf tag update karna selected payload initialize karna nahi hai.
Upar compound-literal update complete new tagged value supply karti hai; next lesson us syntax ko explain karega. Isse threads ke beech atomic synchronization nahi milti. Pointer payload ke liye selected alternative ka specific ownership contract bhi chahiye.
3. Doosra member read karna numeric conversion nahi
C mein most recently written member se alag member read karna union rules ke under corresponding object representation reinterpret karta hai. Result representations par depend karta hai aur trap representation involve kar sakta hai. value.ratio store karne ke baad value.count ko floating value se integer conversion ka portable tareeka na samjhein. Numeric conversion C ke value-conversion rules use karti hai.
Yeh permission relevant union-access rules ke liye specific hai. Unrelated pointer freely cast karke dereference karna alignment aur effective-type requirements violate kar sakta hai. Union saare aliasing rules ka general escape hatch nahi aur uski bytes universal hardware-independent encoding nahi.
4. Common prefix ka limited special rule hai
Optional: common initial sequence
struct CountRecord { int kind; int count; };
struct RatioRecord { int kind; double ratio; };
union Record { struct CountRecord count; struct RatioRecord ratio; };
union Record item = {.count = {1, 7}};
int kind = item.ratio.kind;
Union ke dono structure members compatible int kind se shuru hote hain. Union currently un structure types mein se ek contain kare toh completed union type ki declaration visible hone wali jagah C common-initial-sequence rule se common initial part inspect karne deta hai. Aage ke int aur double members compatible prefix extend nahi karte. Yeh specified exception hai, har alternate member read karne ki permission nahi.
5. Anonymous members access syntax change karte hain
C11 ne anonymous structure aur union members add kiye: untagged structure ya union definition jisme member declarator nahi hota. Unke members enclosing object se extra member name ke bina access ho sakte hain. Isse tagged-union interface shorter ho sakta hai, lekin automatic tag, extra payload lifetime ya correct selected member ki validation nahi milti. Earlier example grouping clear rakhne ke liye union member ko data naam deta hai.
Primary references aur aage padhne ke liye
- WG14 N1570 — public C11 committee draft: 6.5.2.3p3–p6 (including footnote 95), 6.7.2.1. C17 baseline ke stable core rules; yeh final ISO publication nahi hai.
Aage badhne se pehle
- 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.
In ideas ko alag rakhein
- Tag value / Enforced invariant
- Tag write karne se matching union member automatically initialise ya contradictory record validate nahi hota.
Tagged union ka chosen form aur data consistent rakhne ke liye update ko kya karna chahiye?
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
- 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
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.