From: Dave Plonka <dave@plonka.us>
To: tuhs@tuhs.org
Subject: [TUHS] Re: SNOBOL and progeny [Was: Re: Re: Line Numbers Before SysIII nl? BSD num?]
Date: Fri, 29 Jul 2022 10:37:38 -0500 [thread overview]
Message-ID: <CANPwAQZ90tx2e5ABjWZ=WU-kgYCaupWiHQ9dz949QEF0y+-qpg@mail.gmail.com> (raw)
In-Reply-To: <19b82d6e-6b8e-7b49-69ca-e63d0e3c5856@riddermarkfarm.ca>
SNOBOL influenced Dick Haight's bs(1) programming language which
includes some SNOBOL features, a replacement, written in C, for Ken
Thompson's bas(1) BASIC implementation, written in assembly language.
bs (programming language)
https://en.wikipedia.org/wiki/Bs_(programming_language)
BS: a mysterious Unix programming language!
https://www.youtube.com/watch?v=ELICIa3L22o
Although I know of no applications written in bs(1), it remains to
this day in licensed System V Unix variants such as HP-UX and AIX.
Peace,
Dave
On Thu, Jul 28, 2022 at 7:22 PM Stuff Received <stuff@riddermarkfarm.ca> wrote:
>
> On 2022-07-27 21:03, Phil Budne wrote:
> >> Anyway, I have got Phil Budne's implementation
> > C'est moi! SNOBOL came out of Bell Labs in Holmdel NJ.
> > There was a SNOBOL3 implementation in Unix 6th Edition days called "sno".
> >
> > As far as I know Macro SNOBOL4 (that my CSNOBOL4 is a port of) never
> > was ported to the PDP-11 (just not enough address space), but there
> > was a proposal (at least) for a SNOBOL4 implementation for the '11
> > called ELFBOL.
> >
> > Macro SPITBOL (a faster implementation of SNOBOL4) was available on
> > the Research Unix VAXen (Andrew Koenig did a C-like preprocessor
> > called SNOCONE -- SNOBOL with some sugar).
> >
> > Phil
>
> I recall seeing ICEBOL card packs at the U. of Toronto Computing Centre
> decades ago but I know nothing more.
>
> N.
--
dave@plonka.us http://www.cs.wisc.edu/~plonka/
prev parent reply other threads:[~2022-07-29 15:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 2:57 [TUHS] Line Numbers Before SysIII nl? BSD num? segaloco via TUHS
2022-07-23 5:56 ` [TUHS] " markus schnalke
2022-07-23 7:55 ` segaloco via TUHS
2022-07-23 11:01 ` Dan Cross
2022-07-23 11:20 ` John Cowan
2022-07-23 12:00 ` Dan Cross
2022-07-23 12:49 ` Norman Wilson
2022-07-23 13:20 ` Rob Pike
2022-07-23 13:36 ` Ralph Corderoy
2022-07-23 14:33 ` John Cowan
2022-07-24 19:45 ` Warner Losh
2022-07-24 20:33 ` segaloco via TUHS
2022-07-24 21:04 ` Warner Losh
2022-07-23 17:35 ` Clem Cole
2022-07-23 18:40 ` Phil Budne
2022-07-23 18:51 ` Nelson H. F. Beebe
2022-07-23 19:07 ` Douglas McIlroy
2022-07-24 19:02 ` Tomasz Rola
2022-07-28 0:30 ` Tomasz Rola
2022-07-28 1:03 ` Phil Budne
2022-07-28 4:13 ` [TUHS] SNOBOL and RATSNO William H. Mitchell
2022-07-29 4:28 ` [TUHS] " Dave Horsfall
2022-07-29 5:07 ` Tomasz Rola
2022-08-09 5:12 ` Jonathan Gevaryahu
2022-08-09 6:11 ` Rob Pike
2022-08-09 13:34 ` Clem Cole
2022-08-09 15:15 ` Andrew Hume
2022-08-09 18:26 ` Clem Cole
2022-08-09 18:52 ` Tom Teixeira
2022-08-09 21:25 ` Rob Pike
2022-08-09 15:39 ` Richard Salz
2022-08-09 13:56 ` Larry McVoy
2022-08-09 16:45 ` William H. Mitchell
2022-07-29 0:22 ` [TUHS] SNOBOL and progeny [Was: Re: Re: Line Numbers Before SysIII nl? BSD num?] Stuff Received
2022-07-29 5:01 ` [TUHS] " Charles H. Sauer
2022-07-29 14:07 ` John Cowan
2022-07-29 15:37 ` Dave Plonka [this message]
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='CANPwAQZ90tx2e5ABjWZ=WU-kgYCaupWiHQ9dz949QEF0y+-qpg@mail.gmail.com' \
--to=dave@plonka.us \
--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).