How Is a Programming Language Standardized?
summary
Describes how C++ becomes an international standard: proposals start small and are reviewed across 14 study groups and 4 working groups, with over 4,400 public papers and decisions made by consensus rather than majority vote. Explains the committee process—6-day meetings 2–3 times per year with ~120 participants, national bodies resolving comments and a two-round vote—and how timelines, backward-compatibility constraints, and concrete library and parallelism proposals shape what changes.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:11Why standardize languages
- 4:43Portability in programming
- 10:23Who defines a language
- 15:44Standards bodies
- 19:25ISO subcommittee work
- 22:35C++ committee structure
- 26:27C++ standardization history
- 31:43Voting and volunteers
- 39:50Standard evolution process
- 46:53Conclusions and C++ future
- 49:43Q&A
related talks
01h 25mGrill the C++ committee
57mHow To Implement the C++ Standard Library - (Part 1 of 2)
01h 44m"The Evolution of C++ Past, Present and Future"
01h 10mThe Past, Present and Future of Programming Languages
57mWhy Programming Languages Matter
01h 30mThe Past, Present and Future of Programming Languages
31m“New standards to the rescue: the view through an IDE’s glasses”
01h 23mCarbon Language: An experimental successor to C++