Talk:ALGOL 58

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Mid-importance).
	This article is supported by Early computers task force (assessed as Mid-importance).

ZMMD paragraph confusing[edit]

I have two questions about this paragraph:

By the end of 1958 the ZMMD-group had built a working ALGOL 58 compiler for the Z22. ZMMD said Zürich (ie. Rutishauser), München (ie. Bauer, Samelson), Mainz (ie. Z22), Darmstadt (ie. Bottenbruch).

What is the ZMMD-group?
What does the second sentence mean?

Riordanmr (talk) 19:38, 16 February 2008 (UTC)[reply]

Heinz Rutishauser, Friedrich L. Bauer, Hermann Bottenbruch, and Klaus Samelson teamed up to develop the compiler.

ZMMD is an abbreviation for Zürich, München, Mainz, Darmstadt – for Heinz Rutishauser was professor at the ETH Zurich, Friedrich Bauer and Klaus Samelson both worked in Munich, the Z22 which they built it for stood in Mainz, and Hermann Bottenbruch was a mathematician from Darmstadt.

Sincerely, 217.236.218.232 (talk) 23:46, 26 March 2008 (UTC)[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on ALGOL 58. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

Added archive https://web.archive.org/web/20120422070035/http://conservancy.umn.edu/bitstream/107106/1/oh128flb.pdf to http://conservancy.umn.edu/bitstream/107106/1/oh128flb.pdf

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 05:09, 1 October 2016 (UTC)[reply]

SUBALGOL[edit]

Was the SUBALGOL compiler on the Stanford 7090 called BALGOL at the time? I remember knowing about a BALGOL compiler at Stanford, not one called SUBALGOL. Gah4 (talk) 01:25, 22 November 2020 (UTC)[reply]

Atlas Autocode and Imp[edit]

I'll mention this in Talk because I don't have the reference to hand: I believe when Tony Brooker invented Atlas Autocode it was in direct response to Algol58 and in competition with Algol60, rather than being a response to Algol60 as I have seen posted elsewhere. I don't know if being a response to a language counts as a version of the language - maybe not, but they certainly have a lot in common. (For comparison, do you consider C to be a variation of BCPL? Probably not. It was influenced by it and in response to it, but not obviously a dialect of it - same as the relationship between Algol58 and Atlas Autocode.) Atlas Autocode on the other hand morphed into Imp in a smooth continuum, with the name change happening only after sufficient incremental changes had been made that it looked like a new name was needed! — Preceding unsigned comment added by 70.124.38.160 (talk) 21:28, 17 April 2022 (UTC)[reply]