From: Lars Brinkhoff <lars@nocrew.org>
To: Sebastien F4GRX <f4grx@f4grx.net>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Software written in B
Date: Wed, 07 Jun 2023 10:38:12 +0000 [thread overview]
Message-ID: <7wy1kv5zhn.fsf@junk.nocrew.org> (raw)
In-Reply-To: <1e651370-3ada-e211-c277-409d6563500d@f4grx.net> (Sebastien F4GRX's message of "Wed, 7 Jun 2023 12:14:14 +0200")
Sebastien F4GRX wrote:
> And here is my question, is any of you aware of original B source code
> archives? or are in touch with people that would know?
Not for Unix, but.
Steven Johnson went on a sabbatical from Bell Labs to Waterloo
University and took B with him. A group of people there formed a
company which still offers B for GCOS.
https://www.thinkage.ca/gcos/expl/b/manu/manu.html
The original AberMUD was written by Alan Cox (of Linux fame) et al in B.
A paper listing exists but has yet to be scanned. I collected some
scraps here:
https://github.com/larsbrinkhoff/abermud/tree/master/abermud1
Some other people also writing B compilers:
https://github.com/aap/b
https://github.com/DavidSkrundz/B
next prev parent reply other threads:[~2023-06-07 10:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 10:14 [TUHS] " Sebastien F4GRX
2023-06-07 10:38 ` Lars Brinkhoff [this message]
2023-06-07 15:05 ` [TUHS] " Angelo Papenhoff
2023-06-07 15:57 ` Clem Cole
2023-06-07 16:21 ` Lars Brinkhoff
2023-06-07 17:26 ` Bakul Shah
2023-06-07 18:16 ` Phil Budne
2023-06-07 23:49 ` Andrew Hume
2023-06-08 2:10 ` segaloco via TUHS
2023-06-08 3:31 ` Phil Budne
2023-06-08 15:05 ` segaloco via TUHS
2023-06-14 11:51 ` Angelo Papenhoff
2023-06-14 20:03 ` Angelo Papenhoff
2023-06-14 21:53 ` segaloco via TUHS
2023-06-14 22:05 ` Angelo Papenhoff
2023-06-15 8:00 ` Sebastien F4GRX
2023-06-15 8:21 ` Angelo Papenhoff
2023-06-15 8:33 ` Sebastien F4GRX
2023-06-17 8:19 ` Angelo Papenhoff
2023-06-19 9:52 ` Sebastien F4GRX
2023-06-19 10:18 ` Sebastien F4GRX
2023-06-19 10:48 ` Lars Brinkhoff
2023-06-19 10:55 ` G. Branden Robinson
2023-06-19 11:07 ` Sebastien F4GRX
2023-06-19 18:44 ` segaloco via TUHS
2023-06-23 10:59 ` Angelo Papenhoff
2023-06-23 13:32 ` Sebastien F4GRX
2023-06-23 14:01 ` Angelo Papenhoff
2023-06-23 14:14 ` Sebastien F4GRX
2023-06-23 14:39 ` Angelo Papenhoff
2023-06-23 14:10 ` Sebastien F4GRX
2023-06-23 14:49 ` Angelo Papenhoff
2023-06-23 15:31 ` Sebastien F4GRX
2023-06-23 15:36 ` Angelo Papenhoff
2023-06-23 15:53 ` Sebastien F4GRX
2023-06-08 14:41 ` arnold
2023-06-09 8:56 ` Sebastien F4GRX
2023-06-09 9:57 ` 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=7wy1kv5zhn.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=f4grx@f4grx.net \
--cc=tuhs@tuhs.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).