9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Greg Hudson <ghudson@MIT.EDU>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the declaration of main()
Date: Sat, 28 Apr 2001 11:54:13 -0400	[thread overview]
Message-ID: <200104281554.LAA13061@egyptian-gods.MIT.EDU> (raw)
In-Reply-To: Your message of "Fri, 27 Apr 2001 16:22:31 GMT." <3AE99688.96A84266@arl.army.mil>

(In the futile hope of bringing this thread to an earlier close:)

Douglas Gwyn wrote:
> All that fighting a well-established standard does is to isolate you
> from the rest of the world.  Do you really think that there is no C
> code of value except for whatever has been constructed specifically
> for Plan 9?

You're questioning the basic assumption of Plan 9, which is: let's try
to make an interesting and elegant system by abandoning the base of
existing Unix and ANSI C software and making all the design decisions
as if in a vacuum.  The system looks a little like Unix and the
language looks a lot like C only because there's some overlap between
the designers of Plan 9 and the designers of Unix and C.

Yeah, Plan 9 is unlikely to achieve a significant market position as a
result, but that's okay; it's a research project.  If you think people
shouldn't do this kind of research, fine, but you're not going to
convince them to stop by holding extended conversations on their
mailing list.  (Particularly not by sparring with the misguided fans
who really do think there isn't much C code of value apart from what
the Plan 9 group has written, or who think that the ANSI C committee
was populated largely by untrained monkeys.)

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.


  parent reply	other threads:[~2001-04-28 15:54 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 [this message]
2001-04-28 16:39         ` Dan Cross
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=200104281554.LAA13061@egyptian-gods.MIT.EDU \
    --to=ghudson@mit.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).