The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Win Treese <treese@acm.org>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] where did "main" come from?
Date: Fri, 22 May 2020 19:58:31 -0400	[thread overview]
Message-ID: <8B69B753-0713-430E-8A1A-AE23206127AC@acm.org> (raw)
In-Reply-To: <5cef3bd0-5dfc-2d4a-cdde-9d7b03dea353@telegraphics.com.au>



> On May 22, 2020, at 7:33 PM, Toby Thain <toby@telegraphics.com.au> wrote:
> 
>> As for your BCPL question, START() was way I learned it.  I think I
>> first saw it on the 360s or maybe the 1108; but really never did much it
>> until I saw the first Altos. 
> 
> This chart could lead to some predictable conclusions, don't know if
> they are correct:
> 
> https://books.google.com/ngrams/graph?content=main+program&year_start=1930&year_end=2008&corpus=17&smoothing=3&share=&direct_url=t1%3B%2Cmain%20program%3B%2Cc0

This is straying way off topic, but I thought it would be interesting to look at a couple of older sources about it, say, from the late 1940s when there were computers with programs.

A search on Google Books in the date range 1800-1950 gives a lot of hits (at least 10 screens worth). Since it’s Google, your results may vary, but here are the first few I got:

- US Congress hearings on National Health Program, 1946: "Any discussion on either the main program or the amendment to…” Fair enough. Got the phrase, it’s in the range. Just not relevant to the current investigation.

- C Programming: Test Your Skills by Ashok Kamthane, dated by Google Books to 1900

- Information Circular, dated 1925, with the excerpt starting “It consists of a main program, two subroutine subprograms, A macro-flow chart of the program is shown on figure A-1”. Which seems odd, because that pretty clearly isn’t really from 1925. So I clicked through the document, which turns out to be Information Circular 1601: Corrosion Resistance of Metals in Hot Brines: A Literature Review” published by the US Bureau of Mines in 1973.
It also does not have the excerpt in the document.

- Programming Techniques Through C: A Beginners Companion by M. G. Venkateshmurthy, dated 1900.

- Technical Bulletin, Issues 206-216, dated 1922 with the excerpt "The main program (MAIN) will be discussed first and then each of the subroutines called by the main program. Sometimes the subroutines called by the main program call other subroutines.”. Clicking through to it gives the response “No results in this book for ‘main program’”. This turns out to be incorrect, because somewhere between the Google Books server and my Safari browser the search string was mishandled. Changing it in the search box gives 3 snippets referencing “main program”, and the document is apparently about a FORTRAN program compiled with the CDC6400 FTN version 3 compiler. However, nothing more than the snippets is available and the 1922 date is obviously wrong.

Remaining items on the first page are similarly clearly misdated or about non-computer main programs.

No one said archival research is easy, but Google Books does present itself as having better data than it delivers.

- Win



  reply	other threads:[~2020-05-22 23:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 18:43 Lawrence Stewart
2020-05-22 20:01 ` Michael Kjörling
2020-05-22 21:52 ` Clem Cole
2020-05-22 22:00   ` Rob Pike
2020-05-22 23:33   ` Toby Thain
2020-05-22 23:58     ` Win Treese [this message]
2020-05-22 22:08 ` Charles Anthony

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8B69B753-0713-430E-8A1A-AE23206127AC@acm.org \
    --to=treese@acm.org \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).