YOUR C LEARNING COMPANION

Kahan se padhein?

Learning path
C ka contextChapter 68 of 73

C ki timeline: history, editions aur standards

C ki development aur published revisions trace karein; nicknames, dates, drafts aur compiler modes separate karein.

6 min readFoundationsHistory + standards
Offline reading
Is chapter mein9 sections

C ki kai published editions aayi hain. Revision ka nickname, publication year aur compiler mode alag dates ya names use kar sakte hain. Timeline se purani explanation ka context aur applicable rules check kar sakte hain.

1. C earlier languages aur Unix ke saath develop hui

BCPL, B aur C related languages hain, ek unchanged language ke teen names nahi. Richer type model se C characters, integers, pointers aur structured data describe kar saki aur systems work mein useful rahi. PDP-11 environment ne early choices influence kiye; language ko baad mein doosre targets ke liye adapt kiya gaya.

Ritchie ka account early creative period aur later portability work alag karta hai. Unix kernel ka C rewrite usefulness demonstrate karta tha; isse har C program har computer par unchanged run hona prove nahi hota. Beginner narrative ke liye origins chapter dekhein.

2. Milestones aur unke changes

Period / publicationMilestoneMeaning
1960s / 1969–1970BCPL → BMartin Richards ki BCPL aur Ken Thompson ki B, C ki development lineage hain.
1971–1973C developsRitchie C ka type structure develop karte hain; 1972 key creative period hai, ek instant invention nahi.
1973PDP-11 Unix kernelKernel rewrite practical systems use dikhata hai; later portability work phir bhi required hai.
1978 / 1988K&R editionsFirst book evolving language describe karti hai; second standardization period reflect karti hai. Book edition ISO revision nahi.
1983ANSI X3J11Committee standardization shuru karti hai; C ko zero se invent nahi karti.
1989 / 1990C89 / C90ANSI X3.159-1989 ke baad ISO/IEC 9899:1990 aati hai; names usually same foundational standardized revision identify karte hain.
1995C95 amendment1990 standard ka amendment international-character library facilities aur alternative tokens jaise additions laata hai.
1999C99// comments, mixed declarations/statements, inline aur VLAs jaise features add hote hain; later revisions kuch support requirements adjust karti hain.
2011C11Memory model, atomic/thread facilities, generic selection aur static assertions add hote hain; kuch facilities conditional hain.
2018C17 / C18ISO/IEC 9899:2018 C11 corrections incorporate karti hai. C17 common nickname hai; C18 publication year follow karta hai.
2024C23Commonly C23 kehne wali revision ISO/IEC 9899:2024 ke roop mein publish hoti hai; declaration, preprocessing aur library additions hain.
2026 checkC2y workWG14 next main revision ko unpublished list karta hai. Drafts, proposals aur separate technical specifications ka apna status hai.

3. Book, draft aur standard ke alag jobs hain

Published standards revision us edition ka language/library contract specify karti hai. Committee draft specific stage ki wording hai; final publication se differ kar sakti hai. Proposal change suggest karta hai aur reject/revise ho sakta hai. Compiler extension selected ISO edition ka part hue bina useful ho sakti hai.

Separate Technical Specification ek aur publication hai, main C standard ka automatic part nahi. 31 October 2026 ke check mein WG14 C23 ko published aur C2y ko ongoing work list karta hai. Project page N3220 ko early C2y draft bhi identify karta hai; har newer draft ko “C23 standard” bolna distinction mita dega.

4. Nicknames aur publication years alag ho sakte hain

C17, 9899:2018 ke roop mein aur C23, 9899:2024 ke roop mein published hain. Nickname ISO date rewrite karne ka instruction nahi. Tutorial ka “C17” aur catalogue ka “2018” contradictory hona zaroori nahi. Edition aur relevant rule dekhein, page par sabse bada year nahi.

Optional: selected compiler mode inspect karein

Complete C17 example implementation ka standard-version macro defined hone par print karta hai. Displayed GCC commands explicitly C17 select karte hain; yeh toolchain convention hain, C source syntax nahi.

C17 · project file · version.c
#include <stdio.h>
#include <stdlib.h>

int main(void)
{
#ifdef __STDC_VERSION__
    if (printf("%ld\n", (long)__STDC_VERSION__) < 0) return EXIT_FAILURE;
#else
    if (puts("No __STDC_VERSION__ macro") == EOF) return EXIT_FAILURE;
#endif
    return fflush(stdout) == EOF ? EXIT_FAILURE : EXIT_SUCCESS;
}
GCC / GNU tools · example commands
gcc -std=c17 -pedantic-errors -Wall -Wextra version.c -o version
./version

Selected C17 mode mein output 201710 hai. C99 ka 199901L, C11 ka 201112L aur conforming C23 mode ka 202311L hai. Older preview mode draft value report kar sakta hai. Macro akela har optional header, target rule ya runtime facility ka inventory nahi.

5. Older resource ko responsibly kaise padhein

Intended edition identify karein, historical syntax ko current rules se separate karein aur changed facilities current reference mein check karein. Old implicit function declarations aur identifier-list definitions yahan C17 teaching style nahi hain. Compiler ka extension accept karna us mode ki evidence hai; construct ko portable C label karne ka reason nahi.

Old explanation ka contract ab bhi hold karta ho toh use rakhein. Prototypes, const/constexpr, allocation, initialization, enums aur library support jaise version-sensitive topics C23 migration chapter se recheck karein.

6. Thought check: newer-looking document sabko supersede karta hai?

Working draft published standard ke baad dated hai. Kya uske saare rules published C23 hain?

Nahi. Draft kis revision ko target karta hai aur change ka status kya hai, dekhein. Draft future work describe kar sakta hai; separate specification separate reh sakti hai. Publication aur implementation availability alag sawaal hain.

Sources aur aage ki reading

Aage badhne se pehle

  • C ki published editions aur working drafts ka status alag hai.
  • C23 jaisa nickname ISO publication year se different ho sakta hai.
  • Older resource ko intended edition aur current implementation support ke context mein padhein.
In ideas ko alag rakhein
Proposal / Published standard
Discussed ya adopted proposal ko selected published edition aur relevant implementation conditions ke against check karein.
Apne words mein samjhaayein

Older book ya compiler preview feature use karne se pehle kaunsi dates aur version claims check 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.

Purana C example padhte waqt language edition kyun identify karein?
Har choice ki explanation padhein
  1. Har purana convention modern C mein required hai.

    Historical practice aur current language requirement alag hain.

  2. Editions ke beech rules aur available features alag ho sakte hain.

    ✓ Sahi reasoning. Example ko portable rule maanne se pehle edition aur assumptions check karein.

  3. Sirf publication date compiler support prove karti hai.

    Implementation support standard ki publication se separately check karna hota hai.

General

Earlier edition ka quick reference

Existing section links aur saved passages ke liye retained. Exact corrections source review mein documented hain.

C ki evolution practical needs aur platforms ke across portability tatha consistency ki demand — dono ko reflect karti hai. Neeche di gayi timeline language ke development ke key milestones ko highlight karti hai:

  • 1960s: Martin Richards ne BCPL develop ki.
  • 1969–1970: Ken Thompson Bell Labs mein B develop karte hain.
  • 1972: Ritchie ke C aur uske type system ke development ka important saal; language aage bhi evolve hoti hai.
  • 1973: PDP-11 ke Unix kernel ko C mein rewrite kiya gaya, jisse system implementation ke liye language ki usefulness demonstrate hui.
  • 1978: Brian Kernighan aur Dennis Ritchie ne "The C Programming Language" (K&R C) publish ki, jo language ka pehla widely available description tha.
  • 1983: C ko standardize karne ke liye ANSI X3J11 committee form hui.
  • 1989: ANSI C (C89) standard publish hui, jisne common language aur library specification provide ki, specified implementation choices retain karte hue.
  • 1990: ISO ne ANSI C ko ISO/IEC 9899:1990 (C90) ke roop mein adopt kiya.
  • 1999: C99 standard ne variable-length arrays, inline functions, aur single-line comments jaisi features introduce kin.
  • 2011: C11 standard ne multithreading support, atomic operations, aur behtar Unicode handling add ki.
  • 2018: C17 standard, ek maintenance release thi jisne C11 ke issues ko clarify aur fix kiya.
  • 2024: C23 standard ne nullptr, binary literals, digit separators, aur aur bhi library improvements jaisi modern features introduce kin.

Har standard apne predecessor ke upar build hui hai — language ko refine karte hue, safety aur portability ko enhance karte hue, aur modern software development ki zarooraton ko respond karte hue.

Agla idea padhne ke liye tayyar?

Mark this chapter as read whenever you feel ready.

CHAPTER 68 / 73

Is chapter mein

C ki timeline: history, editions aur standards

Search all 73 chapters in both languages.EN + HG

Try “pointer”, “why int”, or “undefined behavior”.

Concepts connect. Follow your curiosity.↑ ↓ to explore · Enter to open
MAKE YOURSELF COMFORTABLE

Your reading space

Appearance

A clear canvas with balanced contrast.

Text size

100%
AA

Reading tools

Your data stays in this browser

Export a backup before changing browsers or replacing an older version of the reader.

YOUR PERSONAL MARGINS

My notebook

Saved on this device
A LITTLE CLARITY

The glossary

A starting meaning, then a chapter to go deeper.

A QUICK DEFINITION

A little clarity

Read the full explanation →

A thought worth keeping