C ka influence: languages, runtimes aur interfaces
Shared history, familiar syntax, implementation language aur foreign interfaces separate karein.
Is chapter mein10 sections
Language C jaisa syntax le sakti hai, C mein implement ho sakti hai ya C interface call kar sakti hai. Yeh alag relationships hain. Inhein alag karke C ka influence aur language boundary cross karte code ki responsibilities samjhenge.
1. Chaar relationships ko mix na karein
| Relationship | Example | Kya prove nahi hota |
|---|---|---|
| Historical development | C++ ki shuruaat C with Classes se hui; Objective-C C foundation par messaging add karti hai. | Har current C program har related language mein valid hai. |
| Familiar syntax | Java familiar braces/operators use karti hai. | Same punctuation ke numeric, memory ya evaluation rules same hain. |
| Implementation language | CPython largely C mein written Python implementation hai. | Python programs C source-language semantics use karte hain. |
| Foreign interface | Rust component C ABI se interface declare kar sakta hai. | Foreign call ownership, types aur lifetime ki saari conditions check karta hai. |
2. C aur C++ ki history shared hai, contracts separate
C++ C with Classes work se grow hui aur apne type, object, library aur initialization rules develop kiye. Modern C/C++ separately standardized hain. Source extension aur compiler mode determine karte hain kaunse language rules apply honge; C++ compiler, C compile karne ka neutral substitute nahi.
int value = 7;
void *generic = &value;
int *view = generic;
Original object pointer ka void * se int * conversion C mein permitted hai. Corresponding implicit conversion C++ mein permitted nahi. Isse C pointer har possible address ke liye valid nahi ho jaata: yahan required type/alignment ke saath live int value designate hota hai.
Doosre familiar differences mein ordinary character-constant types aur kuch const declarations ke linkage defaults hain. Aur C23/C++ mein same spelling wale features ka scope same hona zaroori nahi. C23 constexpr functions define nahi karta; C inline ko C rules se padhein.
3. Familiar punctuation reading aid hai, specification nahi
C ke baad Java braces wala loop recognizable lag sakta hai. Isse broad control-flow idea identify karne mein help hoti hai. C ke array bounds, pointer arithmetic, overflow rules, lifetime model ya UB contracts Java mein transfer nahi hote. Java specification apni language define karti hai.
Objective-C ka C foundation uski messaging/object-lifetime facilities ko ordinary ISO C features nahi banata. Additional layer recognize karein; unfamiliar construct ko missing C keyword na samjhein. Language change karte waqt poochhein kaunse rules shared hain aur kaunse sirf familiar dikhte hain.
4. Runtime implementation aur user language alag hain
CPython ki C implementation aur C API extensions ko Python objects ke saath work aur applications ko Python embed karne deti hain. In interfaces ke apne reference, lifetime, error aur threading contracts hain. Yeh saari Python implementations ki definition ya Python syntax ko direct C descendant bolne ka basis nahi.
C se runtime ki native implementation padhna aur foreign boundary ki costs/responsibilities samajhna aasaan ho sakta hai. Python expression reason karne ke liye Python language/implementation documentation use karein; neeche ke C code se guess nahi.
5. Interoperability ko interface contract chahiye
Foreign function interface different languages ke components connect karta hai. ABI platform-specific binary conventions deta hai: argument passing, results, naming, layout aur related details. ISO C har OS/processor ke liye ek universal ABI specify nahi karti.
Rust external declarations explicit foreign boundary ka example hain. Signature declare karna external code ka promise hold hona prove nahi karta. Har boundary par accessible buffer/count, representation/encoding, nullability, lifetime, allocator/release pairing, callback lifetime aur error policy document karein. C string aur higher-level string object sirf name “string” hone se interchangeable nahi.
Small reviewable interface ban sakta hai: explicit counts, clear ownership, accidental structure layout export karne se bachna aur documented calling conventions check karna. Successful link ko semantic compatibility samajhne se pehle opaque data interfaces aur linking/libraries padhein.
6. Habits transfer karein, naye rules verify karein
Problem decomposition, invariants, boundary validation aur observation/proof distinction jaise habits transfer karein. Har language ka ownership, type, numeric, concurrency aur library model dobara seekhein. C knowledge valuable hai, lekin har language ka prerequisite ya specification ka replacement nahi.
7. Thought check: “C mein implemented” ka matlab?
CPython largely C mein implemented hai. Kya Python list ISO C array ban jaati hai?
Nahi. Python list public Python semantics aur implementation ke object model follow karti hai. Native details behavior/performance explain kar sakti hain; Python source operations ko C array operations nahi banati.
Sources aur aage ki reading
- Stroustrup — history and C/C++ distinction
- Java Language Specification — introduction
- Python reference — implementations
- Python C API — extending and embedding
- Rust reference — external blocks
- Apple — archived Objective-C language introduction
Aage badhne se pehle
- Historical influence, similar syntax, implementation language aur foreign interfaces different relationships hain.
- C mein written runtime apni language ko C semantics nahi deta.
- Language boundary par compatible ABI, ownership aur lifetime contracts chahiye.
In ideas ko alag rakhein
- Implemented in C / Defined by C
- Implementation language runtime banane ka tareeka hai; implemented language ki specification replace nahi karti.
Doosri language C par based hai kehne ka kaun-kaun sa different meaning ho sakta hai?
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. Us language ke apne type, lifetime aur operation rules seekhein.
✓ Sahi reasoning. Syntax influence identical behavior establish nahi karta.
- Haan, matching braces ka matlab matching memory rules hai.
Sirf braces poori language ka memory model define nahi karti.
- Haan, C se influenced har language mein har C feature hota hai.
Influence selected ideas ka ho sakta hai, poori language ka nahi.
General
Earlier edition ka quick reference
Existing section links aur saved passages ke liye retained. Exact corrections source review mein documented hain.
C ne kai later languages ke syntax aur systems interfaces ko influence kiya. C++ ki shuruaat “C with Classes” se hui, lekin modern C aur C++ distinct languages hain: valid C automatically valid C++ nahi. Java aur C# familiar braces/operators ke saath managed runtimes use karte hain; Java C-style pointer arithmetic expose nahi karti, jabki C# unsafe contexts mein pointers allow karti hai. Objective-C C foundation par messaging facilities add karti hai. CPython largely C mein implemented hai, lekin isse Python C ka syntactic descendant nahi banta; doosri Python implementations doosri languages use karti hain. Rust aur modern C++ bhi low-level programming needs address karte hain, alag abstractions aur safety tradeoffs ke saath.
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.