From: lars@nocrew.org (Lars Brinkhoff)
Subject: [pups] bringing up the fist C compiler
Date: 06 Sep 2002 12:52:22 +0200 [thread overview]
Message-ID: <85r8g7l7a1.fsf@junk.nocrew.org> (raw)
In-Reply-To: <200209061028.g86AS8s10221@minnie.tuhs.org>
Warren Toomey <wkt at minnie.tuhs.org> writes:
> In article by Lars Brinkhoff:
> > Warren Toomey <wkt at minnie.tuhs.org> writes:
> > > The chist paper doesn't mention NB, which was the missing link between
> > > B and C.
> >
> > How about this?
> >
> > In 1971 I began to extend the B language by adding a character type
> > and also rewrote its compiler to generate PDP-11 machine instructions
> > instead of threaded code. Thus the transition from B to C was
> > contemporaneous with the creation of a compiler capable of producing
> > programs fast and small enough to compete with assembly language. I
> > called the slightly-extended language NB, for `new B.'
> >
> > [...]
>
> Yes that's it!! Where did you find it?
In the chist paper.
--
Lars Brinkhoff http://lars.nocrew.org/ Linux, GCC, PDP-10,
Brinkhoff Consulting http://www.brinkhoff.se/ HTTP programming
next prev parent reply other threads:[~2002-09-06 10:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 5:35 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 [this message]
2002-09-06 11:06 ` Warren Toomey
2002-09-06 8:28 ` Lars Brinkhoff
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 22:54 [pups] Bringing " Carl Lowenstein
2002-09-05 17:47 Al Kossow
2002-09-05 23:21 ` Johnny Billquist
2002-09-05 15:36 Ian King
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
2002-09-05 12:05 ` Johnny Billquist
2002-09-05 16:11 ` Michael Davidson
2002-09-09 21:17 ` Peter Jeremy
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=85r8g7l7a1.fsf@junk.nocrew.org \
--to=lars@nocrew.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).