From: gregg.drwho8@gmail.com (Gregg Levine)
Subject: [TUHS] b remnants?
Date: Fri, 14 Oct 2011 11:53:53 -0400 [thread overview]
Message-ID: <CAC5iaNGrosBzQ+xqGR91zvbPWwknaX0ZYKXwiuqfWmXYj8o6Gw@mail.gmail.com> (raw)
In-Reply-To: <d929334a-a3af-ecdc-903a-de41b86c21d6@me.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
On Fri, Oct 14, 2011 at 11:34 AM, Derrik Walker <lorddoomicus at mac.com> wrote:
> Many, many eons ago, in the early '90's, there was an implementation of B
> for Linux ( I believe it was written in C, ironically enough ). I think it
> was part of a bigger collection of "ancient" software for Linux that use to
> be around in the early Slackware days.
>
> Alas, I have searched for it in the recent past, as I was thinking about
> porting it to OS X for kicks, but it seems to have vanished.
>
> Having an B, implemented in a modern language for a modern OS would be cool.
>
> - Derrik
>
> On Oct 14, 2011, at 10:52 AM, "A. P. Garcia" <a.phillip.garcia at gmail.com>
> wrote:
>
> Hi,
>
> In memoriam, I read The Development of the C Language:
> http://cm.bell-labs.com/who/dmr/chist.html
>
> It talks a bit about how B was originally implemented somewhat like
> ETH Pascal (p-code). Are there any B interpreters or programs in the
> archive?
>
>
> Thank you,
> A. P. Garcia
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
>
Hello!
How early a time period for the Slackware Linux group? (Which is what
I run.) There's a repository of older distributions on the Ibib site,
and a more comprehensive one situated on a mirror in the UK.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
next prev parent reply other threads:[~2011-10-14 15:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 14:52 A. P. Garcia
2011-10-14 15:34 ` Derrik Walker
2011-10-14 15:53 ` Gregg Levine [this message]
2011-10-14 16:35 ` Derrik Walker
2011-10-14 19:17 ` Jeremy C. Reed
2011-10-14 20:08 ` John Cowan
2011-10-14 18:06 ` Tim Newsham
2011-10-15 3:57 ` A. P. Garcia
2011-10-15 4:57 ` Andru Luvisi
2011-10-15 8:54 ` Michael Davidson
2011-10-15 14:12 ` Gregg Levine
2011-11-01 16:24 ` Tim Bradshaw
2011-10-15 6:20 ` Greg 'groggy' Lehey
2011-10-14 18:23 Jason Stevens
2011-10-15 4:20 Jason Stevens
2011-10-15 4:37 ` Gregg Levine
2011-10-15 8:44 ` Michael Davidson
2011-10-15 16:14 Jason Stevens
2011-10-15 16:41 ` Gregg Levine
2011-10-17 16:18 ` Al Kossow
2011-10-17 16:29 ` Gregg C Levine
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=CAC5iaNGrosBzQ+xqGR91zvbPWwknaX0ZYKXwiuqfWmXYj8o6Gw@mail.gmail.com \
--to=gregg.drwho8@gmail.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).