The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@cley.com (Tim Bradshaw)
Subject: [pups] Bringing up the fist C compiler
Date: Thu, 5 Sep 2002 12:19:06 +0100	[thread overview]
Message-ID: <15735.15786.542175.385620@cley.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0209051206000.4341-100000@Tempo.Update.UU.SE>

* Johnny Billquist wrote:

> How? It was written, of course. In assembler. By that time, you already
> had the assembler, an editor, and other commonly used system programs, so
> it's just a case of the normal development cycle.

Is this known or is it deduction?

(In case there is any confusion here: I do understand very well how
compilers can be implemented on naked machines without preexisting
tools (and indeed I've done more-or-less this with assemblers on
microcomputers, ending up with a perfectly fine assembler which used
the wrong opcode names, because we didn't know what the right ones
were...).  So my question `how was x done' is not `I don't understand
how you can do this' but `historically, what were the steps in this
case'. What I'm trying to find out is what the actual course of events
was for C, so I can give glib answers to people (:-))

--tim




  parent reply	other threads:[~2002-09-05 11:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05  8:06 Tim Bradshaw
2002-09-05  8:16 ` Warren Toomey
2002-09-05  9:38 ` Johnny Billquist
2002-09-05  9:41   ` Tim Bradshaw
2002-09-05 10:07     ` Johnny Billquist
2002-09-05 10:15       ` Lars Brinkhoff
2002-09-05 11:19       ` Tim Bradshaw [this message]
2002-09-05 12:05         ` Johnny Billquist
2002-09-05 16:11           ` Michael Davidson
2002-09-09 21:17             ` Peter Jeremy
2002-09-05 15:36 Ian King
2002-09-05 17:47 Al Kossow
2002-09-05 23:21 ` Johnny Billquist
2002-09-05 22:54 Carl Lowenstein
2002-09-06  5:35 [pups] bringing " Dennis Ritchie
2002-09-06  8:14 ` Warren Toomey
2002-09-06  8:56   ` Lars Brinkhoff
2002-09-06 10:28     ` Warren Toomey
2002-09-06 10:52       ` Lars Brinkhoff
2002-09-06 11:06         ` Warren Toomey
2002-09-06  8:28 ` Lars Brinkhoff

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=15735.15786.542175.385620@cley.com \
    --to=tfb@cley.com \
    /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).