From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: "Steve Simon" <steve@quintile.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] main
Date: Mon, 25 May 2020 13:37:21 +0200 [thread overview]
Message-ID: <bb0a5b40abb7a4ef64664ceb034670fe@firemail.de> (raw)
In-Reply-To: <9E3618DA-1B14-4928-826F-4087F02DB783@quintile.net>
>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...
older CC's came with the so-called startup code where one could increase the number of file handle and so on before compiling and linking the resulting .o to the application object files. Of course one could rename the invocation of main to something like beatles. ;-) Even M$ msc supplied the startup code.
-Steve
prev parent reply other threads:[~2020-05-25 11:38 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
2020-05-25 11:37 ` Thomas Paulsen [this message]
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=bb0a5b40abb7a4ef64664ceb034670fe@firemail.de \
--to=thomas.paulsen@firemail.de \
--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).