From: Paul Winalski <paul.winalski@gmail.com>
To: Angelo Papenhoff <aap@papnet.eu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] C entry keyword
Date: Tue, 30 Oct 2018 09:32:23 -0400 [thread overview]
Message-ID: <CABH=_VS2QG35YUeCOsaz4+APZC7efb=T_Sr7GsZNVGKfF9Ud+w@mail.gmail.com> (raw)
In-Reply-To: <20181030091259.GA44474@indra.papnet.eu>
On 10/30/18, Angelo Papenhoff <aap@papnet.eu> wrote:
> On 30/10/18, Steve Simon wrote:
>>
>> “entry” was a reserved word in K&R Ed.1,
>> my personal favourite C trivia. I have never seen it used outside fortran
>> on mainframes though.
>
> I think PL/1 on Multics uses it, which is probably how it "got into" C.
>
PL/1 inherited the concept of routines with multiple entry points from Fortran.
Did the early K&R C compilers actually implement multiple entry point
routines, or was the keyword simply reserved for future use?
-Paul W.
next prev parent reply other threads:[~2018-10-30 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 8:02 Steve Simon
2018-10-30 8:51 ` Lars Brinkhoff
2018-10-30 9:12 ` Angelo Papenhoff
2018-10-30 13:32 ` Paul Winalski [this message]
2018-10-30 13:56 ` Warner Losh
2018-10-30 17:53 ` Paul Winalski
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='CABH=_VS2QG35YUeCOsaz4+APZC7efb=T_Sr7GsZNVGKfF9Ud+w@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=aap@papnet.eu \
--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).