You're also missing a native assembly language.
Programming should be taught from the point of view of writing your own forth interpreter, up through BIOSes, based off of it, then in to higher level languages.
Logical composition, however, should be taught inversely. Take a high level language (SQL comes to mind, yes that's high level in some respects!) and teach how to isolate and logically differentiate between elements.
However I'm also for the more simple base test first.
Show someone a few examples of how to play Mastermind (game), see if it clicks.
Show someone basic register algebra, as one labeled context, and then show them VHDL style flow definition statements as another context. Keep the contexts labeled.
Anyone that can apply those rules to 'play the games' is probably capable of being a programmer; and anyone that doesn't find it fun probably shouldn't /be/ a programmer.
To present the topic in a historical context the students first have to know what was context/standard at that time, under what circumstances the solutions of their time were developed, whether the restrictions still hold etc. In other words: You would have to include half of a "History of Programming Languages" course, since this is surely not common knowledge.
- Fortan
- ALGOL 68
- B
- BCPL
- K&R C (with its historic syntax containing elements that are now disallowed)
- C89/C90
- C95
- C99
- C11
and what reasons there were to introduce the changes/extensions?
My opinion is clear: Teach the most modern version with its best practises and leave away all the historic baggage that is only of historic importance.