PL/M
high-level programming language for Intel microprocessors

PL/M, an acronym for Programming Language for Microcomputers, is a high-level language conceived and developed by Gary Kildall in 1973 for Hank Smith at Intel for the Intel 8008. It was later expanded for the newer Intel 8080.
The 8080 had enough power to run the PL/M compiler, but lacked a suitable form of mass storage. In an effort to port the language from the PDP-10 to the 8080, Kildall used PL/M to write a disk operating system that allowed a floppy disk to be used. This was the basis of CP/M.
History
Kildall was working at the Naval Postgraduate School in Monterey, California in 1973 when he received funds to equip a computer lab, first with MCS-4-based SIM4 and, a year later, the Intel 8008-based Intel Intellec 8. As part of his employment, Kildall was allowed to spend one day a week on his own projects, but soon found himself spending much more than that living in his VW Microbus in the parking lot of the Intel offices on Bowers Avenue in Santa Clara.
One day he went to see Hank Smith, Intel's manager for the tiny microcomputer software department. Kildall explained his idea of making a high level language for the 8008. Smith didn't understand the concept, so Kildall explained that a programmer could write something like X = Y + Z and the program would convert that into several lines of assembler code which would perform this operation. Smith then called one of Intel's customers and asked if they might be interested in such a product, and when they expressed their interest, Smith immediately told Kildall to do it.
“PL/M” enters the record as high-level programming language for Intel microprocessors. Crown Archives preserves that source wording while asking what high-level, programming and language can confirm, complicate or overturn.
Why this record matters
“PL/M” is worth following because a concise public description often conceals a longer documentary argument. Here, high-level, programming and language provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Oct 21, 2025. The linked authority identifier is Q2160963. The Library of Congress control number is sh85102554. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1973.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “PL/M”, its source revision and the description used here.
- Expand the search: follow PL/M primary sources, PL/M archive and high-level research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “PL/M”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “PL/M” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.