From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the declaration of main()
Date: Sat, 28 Apr 2001 12:39:25 -0400 [thread overview]
Message-ID: <200104281639.MAA03463@augusta.math.psu.edu> (raw)
In-Reply-To: <200104281554.LAA13061@egyptian-gods.MIT.EDU>
In article <200104281554.LAA13061@egyptian-gods.MIT.EDU> you write:
>Yes, main() could have been renamed to strmain() or start() or
>whatever. It would have been less elegant (since main is, after all,
>a good name) and ANSI C programs still wouldn't run normally because
>the loader wouldn't know how to invoke main() (since the designers
>don't want to pollute the system with backward compatibility
>features). Really, your issue is not with that particular decision
>but with the basic design goals of the system, and those are unlikely
>to change.
I don't agree that this is what Doug is saying; I think he's just
saying that compatability could have been achieved in a more seamless
fashion. He has a point, and indeed, someone today ran into problems
trying to mix `native' Plan 9 functions with functions taken from the
APE. (Sorry, I didn't pay close enough attention to see who it was!)
Also, you're off on the linker part; he gave an example of a library
function which would, ``do the right thing'' in that arena. (The C
startup code would invoke mains(), taken out of a library, which, in
turn, would call main()).
On a personal note, I think that ``mains()'' is a cool name.
I don't think that anyone is saying that there's no useful software
written under Unix or in ISO C (note, for instance, that awk is brought
in under the APE). The question is more, ``is the APE sufficient for
supportng that software?'' In most cases, I think so. The other part
of the equation, and one which I think Doug is addressing is, ``is the
APE sufficient for writing software to port to other systems?'' Again,
I think so; though I've never tried. True, one cannot easily mix and
match `native' Plan 9 and APE functions, but I think that might be a
good thing.
- Dan C.
next prev parent reply other threads:[~2001-04-28 16:39 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 20:58 forsyth
2001-04-27 9:13 ` Douglas A. Gwyn
2001-04-27 14:48 ` Boyd Roberts
2001-04-27 16:22 ` Douglas A. Gwyn
2001-04-27 18:24 ` William K. Josephson
2001-04-30 9:23 ` Douglas A. Gwyn
2001-04-27 19:38 ` Boyd Roberts
2001-04-28 15:54 ` Greg Hudson
2001-04-28 16:39 ` Dan Cross [this message]
2001-04-28 17:06 ` Boyd Roberts
2001-04-30 9:25 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 12:05 rob pike
2001-04-30 10:44 forsyth
2001-04-28 18:44 forsyth
2001-04-30 9:24 ` Douglas A. Gwyn
2001-04-28 17:57 forsyth
2001-04-28 22:28 ` Dan Cross
2001-04-30 9:25 ` Douglas A. Gwyn
2001-04-27 6:57 nemo
2001-04-26 19:42 Russ Cox
2001-04-26 20:32 ` Dan Cross
2001-04-26 22:03 ` Boyd Roberts
2001-04-27 9:13 ` Douglas A. Gwyn
2001-04-26 18:23 forsyth
2001-04-26 19:17 ` Mike Haertel
2001-04-26 23:50 ` Boyd Roberts
2001-04-27 14:41 ` Douglas A. Gwyn
2001-04-27 15:40 ` Boyd Roberts
2001-04-27 9:12 ` Douglas A. Gwyn
2001-04-24 10:32 rog
2001-04-24 18:03 ` Steve Kilbane
2001-04-24 8:10 forsyth
2001-04-26 15:55 ` Douglas A. Gwyn
2001-04-24 0:59 okamoto
2001-04-24 3:08 ` Boyd Roberts
2001-04-23 19:33 dmr
2001-04-23 11:09 forsyth
2001-04-23 11:31 ` Boyd Roberts
2001-04-24 9:02 ` Douglas A. Gwyn
2001-04-24 12:09 ` Boyd Roberts
2001-04-26 16:05 ` Douglas A. Gwyn
2001-04-26 18:12 ` Boyd Roberts
2001-04-26 23:55 ` Boyd Roberts
2001-04-24 17:43 ` Greg Hudson
2001-04-26 15:55 ` Douglas A. Gwyn
2001-04-12 6:28 okamoto
2001-04-23 8:44 ` Douglas A. Gwyn
2001-04-23 8:48 ` Boyd Roberts
2001-04-12 6:22 YAMANASHI Takeshi
2001-04-12 6:25 ` andrey mirtchovski
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=200104281639.MAA03463@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/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).