From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] b remnants?
Date: Tue, 1 Nov 2011 16:24:00 +0000 [thread overview]
Message-ID: <D4019958-C257-4BD1-9F51-97E784933F1D@tfeb.org> (raw)
In-Reply-To: <CAFCBnZtX8s+s5gXJG+3N7bhjd7iQ42Lrwt-7mKv=1AsUDsXPng@mail.gmail.com>
On 15 Oct 2011, at 04:57, A. P. Garcia 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.
I think there was at least one system which interpreted O-code (ocode?): the BCPL system for the BBC micro. That machine was pretty short of RAM (32k but the screen and OS ate a significant chunk of that, at least in some screen modes) but had a good deal of ROM, and I think the ocode interpreter lived in ROM (as well, I assume as the BCPL compiler, though that might itself have been an ocode program on a floppy, I'm not sure). I learnt BCPL on that platform.
next prev parent reply other threads:[~2011-11-01 16:24 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
2011-11-01 16:24 ` Tim Bradshaw [this message]
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=D4019958-C257-4BD1-9F51-97E784933F1D@tfeb.org \
--to=tfb@tfeb.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).