1,027 karma · joined April 23, 2020
The parent comment is apt. Of course, languages have their own quirks. But, as Christopher Strachey is once claimed to have said, “I use the same language no matter what compiler I run.”
Now what is more likely to be true is that the code is strangely structured (both because structured programming was new then, and because of memory and processor limitations), and also that much of the internal documentation has been lost. I wish the article had been clearer on that.
I have never bought the argument that there should be one modality of input (or output). I'm basically a keyboard guy, but I use a pointing stick, mouse, trackball, or stylus/touchscreen as appropriate. Some applications benefit from direct contact, others really prefer keyboard input. Further, various disabilities prioritize modalities as well: someone may have serious trouble typing or pointing, and visually-impaired people may prefer voice and speech.
So all these rhapsodies of fingers flying across the keyboard or pointing on a touchscreen as the One True Way miss the point. I want my computing devices to support the kind of interaction I want to engage in, which differs from application to application and time to time.
There's an irony about the design of ALGOL 68. It was denounced at the time as being too big a language, with too many experimental features. In fact, the language in the Report is unimplementable, primarily because the lexical syntax is fanciful (there's an actual difference between the roman period and the italic period) and also abstract (so no two implementations actually have the same lexical syntax). I was on the periphery of an ALGOL 68 implementation project that foundered because the goal was to implement every conceivable edge case, include those that could never occur in practice, e.g., x[i] := x[...50 pages of code...] Yet very reasonable subsets (including ALGOL-68R and FLACC) were built. As for the language breadth, arguably C# is much broader, and I haven't heard anyone claim that it is a failure.
As for the Report...there was a time when I understood it cover to cover. But Lindsey and van der Meulen's Informal Introduction presented the whole language at a level understandable to anyone who understood ALGOL 60. van Wijngaarden did the language a terrible disservice when he forced (that is the correct word, I believe) the use of two-level grammars in order to ensure type correctness. Had the Report never existed, the language would have had much more traction.
The irony? Apart from the grossly-overengineered “transput” library—much better adapted to a unit-record and line printer world than our modern world—the one actual experimental feature in the language was the par clause, which provided parallel execution, and relied on semaphores for synchronization. Dijkstra's semaphores.
Context is king.
I have never been able to determine whether Wirth knew of this work, but, given that Richards's 1969 BCPL paper described OCode, I suspect he was aware of it, and that it influenced his design of the Pascal-P compiler. (I am not sure when Intcode appeared, but it was present when I obtained the BCPL compiler in 1972, a year before the Pascal-P release.)
For the record, I am not an AI.
Given that Paterson has stoutly denied ever looking at any CP/M code (and nobody has ever produced any contradicting evidence), it's clear that in his “quick and dirty operating system”, he took the CP/M user documentation and built something with somewhat the same architecture and user-visible behaviour, using his own code, and tailoring it to the somewhat more powerful 8086. OS designers have been doing this for decades: look at the documentation for Univac and RCA lookalikes for System/360 (available on bitsavers), and compare to DOS/360. Or that “hobby” system written by some guy named Torvalds...
The ICAO phonetic alphabet specifically pronounces "4" as "fouwer", and "9" as "niner", so as to increase redundancy on a noisy channel.
The following year, we used the same bigger assignment, but demanded that the students hand in the work for the first half of the assignment by the end of the first week (the markers were told just to check that it had been handed in, but not to mark it). Due date came along, and the overwhelming part of the class handed in acceptable work on time.
One thing that four years of university, perhaps including a study skills course, teaches you is how to manage multiple due dates with several concurrent projects in various stages of completion.