THE SCOPE
Syntax families, interpreters, standards, implementation histories and disputed lineages.
This starting dossier establishes a research remit and reference points for the section. It does not claim to be a comprehensive historical survey. Future articles will identify primary evidence, publication or artifact dates, competing accounts and the limits of verification.
Distinguish specification and implementation
A language reference defines intended behavior; a compiler or interpreter demonstrates particular realized behavior. Both can change at different speeds.
Influence needs a citation
Similar syntax alone is not proof of direct influence. Interviews, design memos, standards, contemporary source code and documented citations carry more weight.
Track the version, not the label
A language name often spans decades of incompatible changes, extensions, runtime behaviors and competing implementations.
OPEN QUESTIONS / NOT ASSUMPTIONS
Questions that guide the reporting.
- 01Which specification edition is being examined?
- 02What implementation and release demonstrate the feature?
- 03Is a claimed influence documented by its designers?
PRIMARY & TECHNICAL REFERENCES
Starting sources
The references below are paths into the evidence, not a claim that every historical question is settled. Each future article will provide its own direct citations and version-specific evidence.
- 01Python — documentation and history docs.python.org
- 02ECMA-262 language specification tc39.es
VERSION RECORD / 1.0
This dossier is revisable.
2026-10-08 — Initial edition. Research scope, evidence lenses, questions and reference starting points published. No external submissions have been reviewed for this initial edition. Future substantive changes should be documented with supporting evidence.
Submit source evidence or a correction →