The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Lawrence Stewart <stewart@serissa.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] where did "main" come from?
Date: Fri, 22 May 2020 17:52:17 -0400	[thread overview]
Message-ID: <CAC20D2PiMiFAw2aFx7Z88vc6npyzD1px9NLvUzFpEUz1HKTZMQ@mail.gmail.com> (raw)
In-Reply-To: <BC361958-C8A0-4F42-8E9D-A3E981749CCC@serissa.com>

[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]

It's interesting, I was thinking about this the other day too.   I
remember talking about the 'main program' in Fortran when I was learning.
I never thought about it when I saw it in C, other than, ok that's how you
pass command line args, which I thought was really clean.   I remember TOPS
and TSS you had to go rummaging around to get to them.

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.

Clem

On Fri, May 22, 2020 at 2:53 PM Lawrence Stewart <stewart@serissa.com>
wrote:

> C main programs define “main”.
> This also seems to be true of B main programs, according to the
> Johnson/Kernighan manual
> The 1967 Martin Richards BCPL manual doesn’t explain how programs get
> started
> The 1974 update from Martin Richards says there should be an OS addendum
> that explains this.
> The 1974 University of Essex BCPL manual says to use START
> The 1979 Parc Alto BCPL manual uses Main and I think that must be
> unchanged from 1972.
> The AMSTRAD BCPL guide from 1986 uses start()
>
>
> So who started “main” and when?  I can’t find an online copy of the Bell
> Laboratories BCPL manual (Canaday/Thompson) from 1969 or anything about how
> to use BCPL on Multics or CTSS.
>
> -L
>
>

[-- Attachment #2: Type: text/html, Size: 2071 bytes --]

  parent reply	other threads:[~2020-05-22 21:53 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 [this message]
2020-05-22 22:00   ` Rob Pike
2020-05-22 23:33   ` Toby Thain
2020-05-22 23:58     ` Win Treese
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=CAC20D2PiMiFAw2aFx7Z88vc6npyzD1px9NLvUzFpEUz1HKTZMQ@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=stewart@serissa.com \
    --cc=tuhs@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).