Structures: related data ka group
Related values ko record type dein; contained members, pointer links, tags aur object identity alag samjhein.
Is chapter mein8 sections
Student record ko kai related details chahiye. Structure in members ko ek type mein saath rakhta hai. Structure type, uske har object aur members mein stored values ko alag samjhenge.
1. Values ko unke relationship ke liye group karein
Structure type members ki ordered collection describe karta hai. Uske objects record ke part ke roop mein members contain karte hain. Array se alag, members ke types different ho sakte hain aur unko element index ke bajay member names se select karte hain. Identifier aur score group karna relationship express karta hai; automatically values validate nahi hoti.
Neeche .id aur .score designated initializers hain: yeh starting member values ko name karte hain. Later lesson initialization syntax ko detail mein samjhayega.
struct Student {
int id;
double score;
};
struct Student learner = {.id = 7, .score = 82.5};
learner.score = 86.0;
First declaration Student tag wala structure type define karti hai. Woh khud student object create nahi karti. Later declaration learner define karti hai, jiska type struct Student hai. Ek jagah braces type ke members describe karti hain aur doosri jagah object ki initial values; difference ke liye surrounding declaration padhein.
- id
- 7
- score
- 86.0
2. Member particular object ka part hai
Do student objects ke separate id aur score members hote hain. score naam saare students ka shared global variable nahi. learner.score us particular object ka member select karta hai. Structure object modifiable ho aur selected member operation allow kare toh assignment us member ki value change karti hai.
struct Point { int x; int y; };
struct Point location = {2, 3};
struct Point *view = &location;
view->x = 5;
Suitable valid pointer ke liye view->x ka meaning (*view).x hai. Parentheses important hain kyunki member access aur unary indirection ki grouping different hai. Arrow memory allocation operation nahi aur null ya stale pointer valid nahi banata. Earlier lifetime aur type requirements ab bhi apply hoti hain.
3. Containment aur pointer relationship alag hain
struct Label {
int id;
char text[4];
};
struct Label label = {.id = 7, .text = "Cat"};
Chaar char elements har struct Label object ke andar stored hain. Initializer string terminator include karta hai. Pointer member iske bajay separately existing target ka pointer value store karega. Decide karein ki record ko data contain karna hai ya sirf refer karna; is choice se copying, lifetime aur ownership change hoti hai.
4. Structure apne type ko point kar sakta hai
struct Node {
int value;
struct Node *next;
};
struct Node tail = {2, NULL};
struct Node head = {1, &tail};
struct Node define hote waqt incomplete type hai. Us type ka pointer allowed hai, isliye next doosre node ko refer kar sakta hai. Same incomplete structure type ka direct member finite complete member layout nahi dega. Example mein dono nodes ordinary local objects hain; sirf link dikhane ke liye dynamic allocation required nahi.
Pointer link next node ko alive nahi rakhta aur free ki responsibility decide nahi karta. Linked lists aur trees ko ownership, traversal aur removal ke extra rules chahiye. Type link express karne deta hai; complete data structure automatically implement nahi karta.
5. Tags, member names aur aliases ke roles alag hain
struct Student mein Student tag hai. C17 mein tag akela ordinary type alias nahi; suitable typedef doosra naam na de toh struct keyword likhein. Har structure ya union mein member names ka apna namespace hota hai. Do separately declared structure types ki member lists same dikhne se types interchangeable nahi ho jaate.
Primary references aur aage padhne ke liye
- WG14 N1570 — public C11 committee draft: 6.2.3, 6.5.2.3, 6.7.2.1, 6.7.2.3. C17 baseline ke stable core rules; yeh final ISO publication nahi hai.
Aage badhne se pehle
- 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.
In ideas ko alag rakhein
- Structure type / Structure object
- Type record shape describe karta hai; separate objects ke member values different ho sakte hain.
Pointer member wale record ko referenced data ki lifetime contract kyun 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
- 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
Earlier edition ka quick reference
Existing section links aur saved passages ke liye retained. Connected explanations ke liye expanded lessons follow karein.
Structures
Ek struct related variables — apne members — ko ek single type ke andar group karta hai. Members ko struct value par . se ya struct ke pointer par -> se access kiya jaata hai. Structures self-referential ho sakte hain, apne hi type ka ek pointer contain karte hue, jo linked lists, trees, aur doosre dynamic data structures ka base hai:
struct Node {
int data;
struct Node *next;
};
Padding aur Alignment
Alignment requirements ke liye structure members ke beech aur end mein padding ho sakti hai. Declared struct Node ke liye sizeof(struct Node) member sizes ke sum se bada ho sakta hai; sirf sizeof(struct) valid C nahi. Members reorder karne se padding badal sakti hai, lekin universally size kam hone ka rule nahi. C11 ka _Alignof(type) type ki alignment query karta hai aur _Alignas object ki alignment specify karta hai; C23 mein alignof aur alignas preferred hain.
Bit-fields
Structure ya union mein unsigned int flag : 1; jaisa eligible integer bit-field ho sakta hai. Bit-fields allocation unit share kar sakte hain. Allocation order aur kuch packing choices implementation-defined hain; allocation-unit alignment unspecified hai. Bit-field ka address nahi le sakte aur us par sizeof apply nahi kar sakte. Hardware-register mapping ke liye target ke documented compiler/ABI aur device rules chahiye; sirf bit width likhne se mapping portable nahi hoti.
Anonymous Structs aur Unions (C11)
C11 anonymous structure ya union member support karta hai: member ka declarator name nahi hota aur uska type bina tag wali struct ya union definition se specify hota hai. Uske members enclosing structure ya union ke members maane jaate hain. Sirf named tag ya typedef name se yeh anonymous-member form nahi banti.
Unions
Union members storage share karte hain; size largest member ke liye sufficient hota hai aur padding include ho sakti hai. C mein most recently written member se alag member read karna corresponding object representation reinterpret karta hai; result representation-dependent hai aur trap representation ho sakta hai. Portable numeric conversion ya fixed byte order assume na karein. Structure members ke liye specific common-initial-sequence rules hain. Yeh unrelated object-pointer types ko freely cast/dereference karne se alag hai, jo effective-type/aliasing rules tod sakta hai.
Enumerations
enum enumerated type aur named enumeration constants define karta hai. Implicit values 0 se shuru hokar 1 se badhti hain, version ke representability rules ke under. C17 mein enumeration constants ka type int hai; enumerated type khud implementation-chosen char, signed integer ya unsigned integer type ke compatible hota hai jo members represent kar sake. C23 fixed underlying types aur expanded rules ke under larger enumerator values add karta hai. C enums C++ scoped enums nahi; implicit integer conversions ho sakti hain.
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.