The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] B Source Code
Date: Tue, 12 Sep 2017 15:24:05 -0400	[thread overview]
Message-ID: <CAC20D2NhqnCoGkfQGRpYJBfNDQ-T+7aXMdz02bo3VopZ5Xs-vQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OaBDuVj=SZQau8wizW+iKdsdEA74wUtGkVZ8sg_-stqQ@mail.gmail.com>

BTW:  Check out:   ybc: a compiler for B <https://github.com/Leushenko/ybc>

On Tue, Sep 12, 2017 at 2:14 PM, Clem Cole <clemc at ccc.com> wrote:

> Poke around the Honeywell archives.  I believe that there was at least one
> implementation of QED and a runoff flavor that I saw.   As I believe Steve
> Johnson has mentioned,iIt was popular at Waterloo at one point - so check
> with the Waterloo folks. In fact, I had thought that Mike Malcom used it
> for Thoth, QNX's predecessor.
>
> On Tue, Sep 12, 2017 at 2:03 PM, Robert Swierczek <rmswierczek at gmail.com>
> wrote:
>
>> Does anyone know of the existence of source code written in B (C's
>> predecessor?)
>>
>> I have encountered a few snippets here and there, but nothing
>> substantial.  The only "real" program that I know of is AberMUD-1.  It
>> looks like there exists a physical print-out of it:
>>
>> https://dropsafe.crypticide.com/article/12714
>>
>> Could it be that this is the only artifact left of this most important
>> "missing link" of C and Unix History?  How can this (and any other B
>> source) be gathered and preserved?
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170912/d90142ea/attachment.html>


  reply	other threads:[~2017-09-12 19:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 18:03 Robert Swierczek
2017-09-12 18:14 ` Clem Cole
2017-09-12 19:24   ` Clem Cole [this message]
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
2017-09-14  3:48 Doug McIlroy
2017-09-14  4:49 ` Larry McVoy
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
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-15 15:21 Noel Chiappa

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=CAC20D2NhqnCoGkfQGRpYJBfNDQ-T+7aXMdz02bo3VopZ5Xs-vQ@mail.gmail.com \
    --to=clemc@ccc.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).