From: gregg.drwho8@gmail.com (Gregg Levine)
Subject: [TUHS] b remnants?
Date: Sat, 15 Oct 2011 10:12:36 -0400 [thread overview]
Message-ID: <CAC5iaNHSuFKuGJDOUh8u2irVXSA7_M8xd=WV6e9sgGDPqBVA_w@mail.gmail.com> (raw)
In-Reply-To: <1318668899.92444.YahooMailClassic@web82407.mail.mud.yahoo.com>
On Sat, Oct 15, 2011 at 4:54 AM, Michael Davidson
<michael_davidson at pacbell.net> wrote:
>
> --- On Fri, 10/14/11, A. P. Garcia <a.phillip.garcia at gmail.com> wrote:
>
> What intrigued me about this is that it's such an early example of an
> abstract machine running as an interpreter. BCPL, roughly
> contemporaneous, used ocode as an intermediate language, but it seems
> this was intended to be further translated into assembly. While it's
> possible to interpret ocode, in practice it seems this was rare, if it
> was done at all.
>
> Not sure if anyone ever interpreted ocode - by the time I encountered BCPL in the mid 1970's the "porting kit" consisted of the BCPL compiler along with an ocode to intcode translator, a reference intcode interpreter written in BCPL and of course, the intcode for the compiler. To bootstrap on a new machine you implemented an intcode interpreter - probably in assembler and, initially, ran the intcode version of the compiler until you had implemented an ocode to machine code translator for your system.
>
> All of this is described in the Richards / Whitby-Strevens book.
>
> Michael Davidson
>
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
Hello!
I just ran a Google search (naturally) using the term BCPL, and found
an interesting set of pages. The Wikipedia page on it contains some
darned interesting things. Take for example the TX0 and TX1 computers.
The PDP-1 descends from one of them.
The first MUD was written using BCPL, which I suspect would be right
down a certain correspondent's alley.
-----
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-15 14:12 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
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 [this message]
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='CAC5iaNHSuFKuGJDOUh8u2irVXSA7_M8xd=WV6e9sgGDPqBVA_w@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).