From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] My Eu paper, mark 2
Date: Mon, 13 Oct 2003 08:58:55 +0000 [thread overview]
Message-ID: <S_mdnc9iIaQYbxuiU-KYuA@comcast.com> (raw)
In-Reply-To: <200310101200.h9AC0A1c031067@ratthing-b246.strakt.com>
Laura Creighton wrote:
> ... C was made by X people,
> Y helping and C++ by Q people, R people helping.
> Anybody here know what X Y Q R are?
Actually small armies did become involved.
The original versions of C and C++ were designed
by single individuals, and implemented by the
same (although C++ required a C implementation);
there is a lot of support structure (linkers,
libraries, debuggers, etc.) that dragged in other
contributors. For example Mike Lesk worked on
the early version of a portable I/O library and
Steve Johnson worked on the Portable C Compiler.
By the time C was "commercial" there were several
people working on it and its surrounding software
generation system. And of course the languages
kept growing, with contributions one way or
another by hundreds.
I think you could reasonably say that a general-
purpose programming language can be designed and
implemented in a limited context by one person
(there are other historical examples), but it
takes significantly more resources to turn it
into an industrial-strength product.
next prev parent reply other threads:[~2003-10-13 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 12:00 Laura Creighton
2003-10-10 22:11 ` Geoff Collyer
2003-10-11 9:21 ` Charles Forsyth
2003-10-11 9:27 ` Geoff Collyer
2003-10-11 21:28 ` Lyndon Nerenberg
2003-10-10 22:12 ` Geoff Collyer
2003-10-13 8:58 ` Douglas A. Gwyn [this message]
2003-10-17 2:58 [9fans] a problem I don't understand on a reinstall Russ Cox
2003-10-17 11:41 ` [9fans] My Eu paper, mark 2 John DeGood
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=S_mdnc9iIaQYbxuiU-KYuA@comcast.com \
--to=dagwyn@null.net \
--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).