From: Clem Cole <clemc@ccc.com>
To: Steve Simon <steve@quintile.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] main
Date: Sun, 24 May 2020 21:12:23 -0400 [thread overview]
Message-ID: <CAC20D2P3WV6w_wG3z6BmPr0kmPTq1xwZwE-x+MV3iprXDgG2aQ@mail.gmail.com> (raw)
In-Reply-To: <9E3618DA-1B14-4928-826F-4087F02DB783@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
No, it’s a FORTRAN-ism. That allows multiple entries into a subroutine.
On Sun, May 24, 2020 at 8:53 PM Steve Simon <steve@quintile.net> wrote:
>
> re: main.
>
> i was surprised not to see any mention of the entry keyword reserved but,
> i believe, never used in early c. it is listed in k&r ed1.
>
> i always assumed this was to allow the author to choose an alternative to
> main() for the program’s entry point, but we all know what assumption is...
>
> -Steve
>
>
> --
Sent from a handheld expect more typos than usual
[-- Attachment #2: Type: text/html, Size: 932 bytes --]
next prev parent reply other threads:[~2020-05-25 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 0:11 Steve Simon
2020-05-25 1:12 ` Clem Cole [this message]
2020-05-25 11:37 ` Thomas Paulsen
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=CAC20D2P3WV6w_wG3z6BmPr0kmPTq1xwZwE-x+MV3iprXDgG2aQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=steve@quintile.net \
--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).