From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] B Source Code
Date: Wed, 13 Sep 2017 21:49:25 -0700 [thread overview]
Message-ID: <20170914044925.GG24549@mcvoy.com> (raw)
In-Reply-To: <201709140348.v8E3mitl090309@tahoe.cs.Dartmouth.EDU>
Doug, could you talk about this some more? Sort of like Reddit's
explain it like I'm 5? Assume I'm dense but want to learn and tell
me how this worked again. Threaded? I'm guessing you mean that it
did paging, did that need threads in the current sense?
On Wed, Sep 13, 2017 at 11:48:44PM -0400, Doug McIlroy wrote:
> > Check out: ybc: a compiler for B <https://github.com/Leushenko/ybc>
>
> >From a historical standpoint, a plain B compiler lacks a very important
> attribute of B in Unix. Yes, B presaged some C syntax. But its shining
> property was that it produced threaded code, for which both compact
> and expanded runtime support was available. The latter had software
> paging. Thus B transcended the limited physical memory of the early
> PDP-11s.
>
> If you can't compile something, you can't run it. A prime example was B
> itself. Without software paging it would not have been able to recompile
> itself, and Unix would not have been self-supporting.
>
> Doug
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2017-09-14 4:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 3:48 Doug McIlroy
2017-09-14 4:49 ` Larry McVoy [this message]
2017-09-14 5:06 ` Lars Brinkhoff
2017-09-14 12:53 ` Ronald Natalie
2017-09-14 5:33 ` Alec Muffett
2017-09-14 5:44 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2017-09-15 15:21 Noel Chiappa
2017-09-14 13:39 Noel Chiappa
2017-09-14 14:24 ` Dan Cross
2017-09-14 19:46 ` Derek Fawcus
2017-09-15 3:59 ` Dave Horsfall
2017-09-15 11:43 ` William Pechter
2017-09-19 1:20 ` Dave Horsfall
2017-09-15 12:44 ` Clem Cole
2017-09-15 13:03 ` Clem Cole
2017-09-12 18:03 Robert Swierczek
2017-09-12 18:14 ` Clem Cole
2017-09-12 19:24 ` Clem Cole
2017-09-12 19:43 ` Steve Johnson
2017-09-18 21:45 ` Angelo Papenhoff
2017-09-19 17:01 ` Thorsten Sideboard
2017-09-12 19:36 ` Charles Anthony
2017-09-12 20:39 ` Robert Swierczek
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=20170914044925.GG24549@mcvoy.com \
--to=lm@mcvoy.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).