The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Angelo Papenhoff <aap@papnet.eu>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Software written in B
Date: Wed, 7 Jun 2023 17:05:27 +0200	[thread overview]
Message-ID: <ZICct/0Yth95iYcY@indra.papnet.eu> (raw)
In-Reply-To: <1e651370-3ada-e211-c277-409d6563500d@f4grx.net>

Sebastien,
I'm not aware of any old UNIX B code beyond the examples from the
documentation and one or two short programs for the PDP-7 (this is older
B).

As Lars already mentioned, some people have written their own B
compilers, even in B.
My compiler (https://github.com/aap/b) generates the same threaded
code that ran on the PDP-11 and I implemented it on a few platforms,
(pdp-11, amd64, mips32, riscv64), notably it runs on UNIX v6. 
Robert Swierczek has written a B compiler that is compatible with the
PDP-7 runtime:
https://github.com/DoctorWkt/pdp7-unix/blob/master/src/other/b.b

With B you pretty much have to write your own code unfortunately. Would
be great if some bigger programs (like the compiler and yacc) were found.

best,
Angelo

On 07/06/23, Sebastien F4GRX wrote:
> Hello everyone,
> 
> this is my first post on this list.
> 
> 
> After looking at the archives for this mailing list, I have seen that 
> the B language has been discussed several times already.
> 
> After viewing Ken Thompson's interview by Brian Kernighan at VCF East 
> 2019, I became interested in the B language, as it seemed full-featured 
> for system programming, close to C, and simple enough to write a parser 
> for it without a code generation tool.
> 
> So for fun and self-education, I am now writing a (or yet another) B 
> compiler, in C, after reading Jack Crenshaw's "Let's build a compiler" 
> documentation ( https://compilers.iecc.com/crenshaw/ )
> 
> Here it is: https://git.sr.ht/~f4grx/bpars
> 
> It is now starting to generate code for the 68hc11 8-bit platform. It 
> can also generate C code.
> 
> 
> I have written some test programs, found some B examples, but I thought 
> it would be great to use my compiler with actual B software.
> 
> Of course, B was a "transition" language, that did not have a continued 
> use as soon as it evolved into C. so if any software remains, it will be 
> quite hard to find.
> 
> 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?
> 
> 
> In particular, I read on this document written by Dennis Ritchie: 
> https://www.bell-labs.com/usr/dmr/www/chist.html
> 
>  > After the TMG version of B was working, Thompson rewrote B in itself 
> (a bootstrapping step).
> 
> 
> I have also read that the YACC tool was initially written in B.
> 
> There might be other historical B sources that I am not aware of.
> 
> 
> Do you know if any of this code has survived to this day? Where could I 
> find more information about this?
> 
> 
> Thank you very much,
> 
> Sebastien Lorquet (F4GRX)
> 

  parent reply	other threads:[~2023-06-07 15:05 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 ` [TUHS] " Lars Brinkhoff
2023-06-07 15:05 ` Angelo Papenhoff [this message]
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=ZICct/0Yth95iYcY@indra.papnet.eu \
    --to=aap@papnet.eu \
    --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).