From: Lassi Kortela <lassi@lassi.io>
To: 9fans@9fans.net
Subject: Re: [9fans] plan 9 and lisp
Date: Mon, 23 Jan 2023 13:45:08 +0200 [thread overview]
Message-ID: <4258fc3c-cc05-22f1-437a-ed44e70feb46@lassi.io> (raw)
In-Reply-To: <CAEE9J-Vc101EGDk27uHZJQj2RvpUjsrgG3pe10D+jRX=7J9gbw@mail.gmail.com>
> Not Plan 9, but lately I've been working in Chicken, which is a lovely
> pragmatic Scheme for *nix: https://www.call-cc.org/ . Perhaps I should
> give s9fes a shot as well!
Chicken and Gambit are the most portable "big" Scheme implementations.
Both come with a Scheme->C compiler and a separate Scheme interpreter.
With luck, it's possible to port them to Plan 9 with modest effort.
People have built recent versions of Chicken with compilers smaller than
GCC and Clang (it was probably tcc). Gambit should be able to target
ANSI C. Both implementations use "green threads".
s9fes and Chibi-Scheme are featherweight by comparison, as is
TinyScheme. All probably easy to port to Plan 9.
s7 is another small interpreter that ships in one .c file and is
actively maintained. Possibly also easy to port.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T7b0afbefb53189b6-M4bf34da27c83338ce49e8014
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-01-23 11:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 7:09 fig
2023-01-19 11:22 ` Lassi Kortela
2023-01-19 15:28 ` ori
2023-01-19 18:26 ` Csepp
2023-01-19 18:33 ` Jacob Moody
2023-01-19 15:57 ` mkf9
2023-01-19 15:47 ` Bakul Shah
2023-01-19 16:01 ` Dan Cross
2023-01-19 16:13 ` Bakul Shah
2023-01-19 17:07 ` Skip Tavakkolian
2023-01-20 19:45 ` Bakul Shah
2023-01-23 11:31 ` Nick LaForge
2023-01-23 11:45 ` Lassi Kortela [this message]
2023-01-25 14:12 ` Ahmed Khaled
2023-01-26 19:34 ` Skip Tavakkolian
2023-01-25 22:59 ` Bakul Shah
2023-01-26 7:18 ` Lassi Kortela
2023-01-26 18:18 ` Tony Mendoza
2023-01-19 11:29 ` Edward Partenie
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=4258fc3c-cc05-22f1-437a-ed44e70feb46@lassi.io \
--to=lassi@lassi.io \
--cc=9fans@9fans.net \
/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).