The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Steve Nickolas <usotsuki@buric.co>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix?
Date: Mon, 31 Jan 2022 12:16:09 -0500	[thread overview]
Message-ID: <CABH=_VS7G1XqO03NRkvSXEr8EiHWWP_sGyRnVNxV9wt3G9W_EQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2201301944370.17970@sd-119843.dedibox.fr>

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.

-Paul W.

"Plugh" (said in a hollow voice)

  reply	other threads:[~2022-01-31 17:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 23:07 [TUHS] " Will Senn
2022-01-28 23:18 ` Dan Cross
2022-01-28 23:31   ` Will Senn
2022-01-29  0:03     ` Rob Pike
2022-01-29  0:40     ` Will Senn
2022-01-29 19:05       ` John Cowan
2022-01-29 19:36         ` arnold
2022-01-29 19:59 ` Clem Cole
2022-01-29 20:02   ` Jon Steinhart
2022-01-29 20:13   ` Bakul Shah
2022-01-29 20:30     ` Clem Cole
2022-01-29 20:34     ` Larry McVoy
2022-01-29 21:03       ` Al Kossow
2022-01-29 21:38         ` Larry McVoy
2022-01-29 22:06       ` Bakul Shah
2022-01-29 22:48         ` GREEN
2022-01-30  3:27           ` Larry McVoy
2022-01-30 16:57   ` David Barto
2022-01-30 18:07     ` [TUHS] Compilation "vs" byte-code interpretation, was " Dan Stromberg
2022-01-30 20:09       ` David Barto
2022-01-31  7:59         ` WEB
2022-01-30 22:51       ` Dan Cross
2022-01-30 23:57         ` Dan Stromberg
2022-01-31  0:23         ` Nemo Nusquam
2022-01-31  0:45           ` Steve Nickolas
2022-01-31 17:16             ` Paul Winalski [this message]
2022-01-31 20:00               ` Erik E. Fair
2022-01-31 22:45               ` Steve Nickolas
2022-02-02  4:53               ` Adam Thornton
2022-01-31  1:41       ` Phil Budne
2022-02-07  3:04   ` [TUHS] " Rob Gingell
     [not found] <A84C7761-A80D-4F8D-B541-2C7F7E5B5E39@hotmail.co.uk>
2022-01-30 20:09 ` [TUHS] Compilation "vs" byte-code interpretation, was " silas poulson

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='CABH=_VS7G1XqO03NRkvSXEr8EiHWWP_sGyRnVNxV9wt3G9W_EQ@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=usotsuki@buric.co \
    /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).