From: Keith Wright <kwright@keithdiane.us>
To: guile-user@gnu.org
Subject: Re: [EXT] Can guile be implementation independent?
Date: Sun, 19 Dec 2021 15:03:01 -0500 [thread overview]
Message-ID: <87r1a84b2i.fsf@fcs22.keithdiane.us> (raw)
In-Reply-To: <91c20674-e4e7-ae31-c33f-072c566312bf@gmail.com> (message from Taylan Kammer on Sat, 18 Dec 2021 18:10:58 +0100)
Taylan Kammer <taylan.kammer@gmail.com> writes:
> On 17.12.2021 18:05, Thompson, David wrote:
>>
>> I think the shortest and easiest answer to this question,
>> in practice, is "no."
>>
>> I prefer to think of each Scheme implementation as its own distinct
>> language,
I hope not.
> The RnRS have some severe limitations. In all RnRS:
>
> - No TCP/IP
> - No POSIX or Win32
> - No threads
>
> In R7RS-small, and R5RS and earlier:
>
> - No hash tables
> - No sub-typing
Do we recoginize a distinction between core language and libraries?
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
>> I wonder why your releases all seem to target Guile 2
>> Will this also work with Guile 3?
>
> New Stuff gets my attention sooner when it is kind to Old Stuff.
Q: Can portable code be run with Guile?
A: If you have to ask Guile-2 or Guile-3 then you can't do it.
(But TTN might.)
-- Keith
next prev parent reply other threads:[~2021-12-19 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 1:42 Can guile be implementation independent? Jacob Hrbek
2021-12-17 2:53 ` Nala Ginrut
2021-12-17 3:01 ` Jacob Hrbek
2021-12-17 3:27 ` Nala Ginrut
2021-12-17 13:32 ` silas poulson
2021-12-17 16:26 ` Dr. Arne Babenhauserheide
2021-12-18 15:30 ` Tim Van den Langenbergh
2021-12-18 18:47 ` Dr. Arne Babenhauserheide
2021-12-17 16:19 ` Maxime Devos
2021-12-17 17:05 ` [EXT] " Thompson, David
2021-12-18 17:10 ` Taylan Kammer
2021-12-19 20:03 ` Keith Wright [this message]
2021-12-19 20:57 ` Taylan Kammer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1a84b2i.fsf@fcs22.keithdiane.us \
--to=kwright@keithdiane.us \
--cc=guile-user@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).