Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Adam Thornton <athornton@gmail.com>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] [TUHS] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix?
Date: Tue, 1 Feb 2022 21:53:50 -0700	[thread overview]
Message-ID: <CAP2nic3Cq5XP2SQy7B=W7VHrin+yqA9dEjYN-X8v2kt_bUDjew@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VS7G1XqO03NRkvSXEr8EiHWWP_sGyRnVNxV9wt3G9W_EQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 655 bytes --]

On Mon, Jan 31, 2022 at 10:17 AM Paul Winalski <paul.winalski@gmail.com>
wrote:

> On 1/30/22, Steve Nickolas <usotsuki@buric.co> wrote:
> > And I think I've heard the Infocom compilers' bytecode called "Z-code" (I
> > use this term too).
> That is correct.  The Infocom games ran on an interpreter for an
> abstract machine called the Z-machine.  Z-code is the Z-machine's
> instruction set.  There is a freeware implementation out there called
> Frotz.
>
>
There's a reasonably functional Frotz implementation for TOPS-20, as it
happens.  The ZIP interpreter was easier to port to 2.11BSD on the PDP-11.

https://github.com/athornton/tops20-frotz

Adam

[-- Attachment #1.2: Type: text/html, Size: 1216 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

           reply	other threads:[~2022-02-02  4:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CABH=_VS7G1XqO03NRkvSXEr8EiHWWP_sGyRnVNxV9wt3G9W_EQ@mail.gmail.com>]

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='CAP2nic3Cq5XP2SQy7B=W7VHrin+yqA9dEjYN-X8v2kt_bUDjew@mail.gmail.com' \
    --to=athornton@gmail.com \
    --cc=coff@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).