Function pointers aur callbacks
Compatible function pointer se behavior ki choice pass karein aur call aur lifetime contracts samjhein.
Is chapter mein8 sections
Kabhi operation ko behavior ki choice leni hoti hai. Sort ko comparison rule aur transformation ko apply karne wala function chahiye. Function pointer surrounding operation rewrite kiye bina yeh choice supply karne deta hai.
1. Pehle function type padhein
int (*operation)(int, int) do ints lekar int return karne wale function ka pointer declare karta hai. Parentheses important hain. int *operation(int, int) pointer return karne wala function declare karta hai. Neeche Operation typedef pointer type ko naam deta hai; naya ownership rule nahi banata.
Function designator ordinarily us function ke pointer mein convert hota hai. Isi liye add ko operation mein assign kar sakte hain; &add bhi likh sakte hain. operation(7, 2) selected function call karta hai. Function ke instructions pointer object mein copy nahi hote.
2. Pointer copy karne se choice copy hoti hai
#include <assert.h>
typedef int (*Operation)(int, int);
static int add(int left, int right) { return left + right; }
static int subtract(int left, int right) { return left - right; }
int main(void)
{
Operation operation = add;
assert(operation(7, 2) == 9);
operation = subtract;
assert(operation(7, 2) == 5);
Operation saved = operation;
operation = add;
assert(saved(7, 2) == 5);
return 0;
}
Upar calls ke small inputs ki sum aur difference int mein fit hoti hain. operation reassign karne se us object ke through later calls ki choice badalti hai. saved pointer ab bhi subtract select karta hai. Yeh object pointers wala value-copy principle hai.
3. Callback supplied behavior hai
Callback doosri operation ko diya gaya function hai, jise woh operation call karti hai. Naam se asynchronous event, new thread ya later time imply nahi hota. Yeh example supplied function ko immediately har element ke liye call karta hai. Surrounding loop traversal karta hai; callback ek value transform karta hai.
#include <assert.h>
#include <stddef.h>
typedef int (*Transform)(int);
static int increase(int value) { return value + 1; }
/* items: count writable ints; transform: valid compatible function.
Every call and stored result must meet that function's contract. */
static void transform_each(int *items, size_t count, Transform transform)
{
for (size_t i = 0; i < count; ++i) items[i] = transform(items[i]);
}
int main(void)
{
int values[] = {1, 2, 3};
transform_each(values, 3, increase);
assert(values[0] == 2 && values[1] == 3 && values[2] == 4);
return 0;
}
4. Call ke liye compatibility required hai
Pointed-to function type actual called function se compatible honi chahiye. Parameter count, types aur return type contract ka part hain. Incompatible function pointer ko cast karna invalid indirect call repair nahi karta. Compiler cast accept kare toh bhi call safe hone ka evidence nahi hai.
Function pointer null ho sakta hai. Callback API ko call se pehle null reject karna ya absence ka meaning define karna chahiye. transform_each contract valid compatible function aur count writable integer elements require karta hai. increase callback ko aisi value chahiye jiska increment int mein fit ho.
5. Shared data ka alag contract hai
C function pointer automatically captured local variables bundle nahi karta. Kuch APIs callback data ke liye separate void * context pointer leti hain. Us pointer ko valid target aur enough lifetime chahiye. API later ke liye callback store kare toh timing, registration ending aur overlapping calls ke rules jaaniye.
void * wala object-pointer round-trip guarantee generally function pointers tak extend nahi hota. Function pointers ko appropriate types mein rakhein. Portable C har pointer kind ka same size ya representation promise nahi karti.
Kya “callback” ka matlab function doosre thread mein run hoga?
Explanation padhein
Nahi. Yeh batata hai ki behavior kaun supply karta hai. Receiving API decide karti hai ki function kab aur kahan call hoga; uska contract padhein.
Primary references aur aage padhne ke links
- WG14 N1570 — public C11 draft: 6.3.2.1, 6.3.2.3, 6.5.2.2, 6.7.6.3: stable C17 function-pointer and call rules.
Aage badhne se pehle
- 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.
In ideas ko alag rakhein
- Callback / Asynchronous execution
- Callback supply karne se khud-ba-khud doosra thread ya later invocation imply nahi hota.
Doosri operation ko callback aur data pointer dene se pehle caller ko kaunsa agreement 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
- 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
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.