From: John Cowan <cowan@ccil.org>
To: Dan Cross <crossd@gmail.com>
Cc: The Unix Heritage Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Question about BSD disklabel history
Date: Tue, 2 Jan 2024 16:17:54 -0500 [thread overview]
Message-ID: <CAD2gp_ToAxFw7cgO9SheSrqTGjqvBffK9+vTx94MhRcqMKeQ8A@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W7VAsQaXGc5YCFQ8m=WcYPyNvsL0dnDdt-fjp8EgLxygw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Tue, Jan 2, 2024 at 3:49 PM Dan Cross <crossd@gmail.com> wrote:
Perhaps the feeling is that that is what FORTH was; for that I
> guess I don't see any reason one couldn't transpile to FORTH from some
> other language.
Henry Baker wrote a beautiful little paper (see
https://www.plover.com/~mjd/misc/hbaker-archive/ForthStack.html>) showing
the mapping between Linear Lisp (a Lisp in which all variables are
referenced once and only once) and a Forth-style "frameless stack". There
is also a discussion of Forth as a set of linear combinators: Manfred von
Thun's Joy <https://en.wikipedia.org/wiki/Joy_(programming_language)> is a
Forth-like using nested lists in which the stack is the top-level list.
>
>
[-- Attachment #2: Type: text/html, Size: 1708 bytes --]
next prev parent reply other threads:[~2024-01-02 21:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 17:30 [TUHS] " Grant Taylor via TUHS
2023-12-31 17:38 ` [TUHS] " arnold
2023-12-31 20:07 ` Warner Losh
2024-01-01 0:13 ` Bakul Shah
2023-12-31 20:27 ` Phil Budne
2023-12-31 21:02 ` Warner Losh
2024-01-01 0:26 ` Grant Taylor via TUHS
2024-01-01 2:22 ` Warner Losh
2024-01-01 3:24 ` Grant Taylor via TUHS
2023-12-31 21:31 ` Clem Cole
2023-12-31 22:07 ` Warner Losh
2024-01-01 16:00 ` Clem Cole
2024-01-02 18:49 ` Warner Losh
2024-01-02 19:30 ` Chet Ramey
2024-01-02 20:07 ` Clem Cole
2024-01-02 19:50 ` Dan Cross
2024-01-02 19:55 ` Jim Capp
2024-01-02 20:11 ` Dan Cross
2024-01-02 20:30 ` Dan Cross
2024-01-02 20:50 ` Clem Cole
2024-01-02 21:04 ` Dan Cross
2023-12-31 22:46 ` G. Branden Robinson
2023-12-31 23:06 ` Larry McVoy
2023-12-31 23:37 ` Al Kossow
2023-12-31 23:41 ` Alec Muffett
2024-01-02 20:48 ` Dan Cross
2024-01-02 21:17 ` John Cowan [this message]
2024-01-03 3:33 ` Theodore Ts'o
2024-01-03 3:57 ` Warner Losh
2024-01-03 4:03 ` Warner Losh
2024-01-03 4:30 ` Theodore Ts'o
2024-01-03 5:10 ` Warner Losh
2024-01-03 15:56 ` Dan Cross
2024-01-03 16:37 ` Theodore Ts'o
2024-01-03 16:41 ` Dan Cross
2024-01-04 8:42 ` arnold
2024-01-04 18:26 ` Kevin Bowling
2024-01-03 14:39 ` Dan Cross
2023-12-31 23:08 ` Phil Budne
2023-12-31 23:37 ` G. Branden Robinson
2023-12-31 23:59 ` Warner Losh
2023-12-31 23:50 ` G. Branden Robinson
2024-01-01 0:09 ` Al Kossow
2023-12-31 21:55 Norman Wilson
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=CAD2gp_ToAxFw7cgO9SheSrqTGjqvBffK9+vTx94MhRcqMKeQ8A@mail.gmail.com \
--to=cowan@ccil.org \
--cc=crossd@gmail.com \
--cc=tuhs@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).