From: Nala Ginrut <nalaginrut@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Re: SRFI 106 "basic socket interface" in Guile
Date: Mon, 25 Oct 2021 14:11:21 +0800 [thread overview]
Message-ID: <CAPjoZocM_R4+6q6q1RpdX+R4yNLqMX_+ZcZwgwOTqOA2YU0h9Q@mail.gmail.com> (raw)
In-Reply-To: <20211025025953.75bi6eo5qxruykes@localhost>
To my experience on implementing the server-core of Artanis with pure
Guile. I think srfi 106 could be mostly covered by the current Guile.
However, I'm not sure about some options as constants.
Best regards.
On Mon, Oct 25, 2021, 13:57 Tim Lee <progscriptclone@gmail.com> wrote:
> I noticed that Guile does not implement SRFI 106 (basic socket interface)
> (https://srfi.schemers.org/srfi-106/srfi-106.html). Is there a
> fundamental reason for the omission? I'm just wondering whether or not
> Guile has all the socket primitives needed to implement SRFI 106.
>
>
next prev parent reply other threads:[~2021-10-25 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 2:59 SRFI 106 "basic socket interface" in Guile Tim Lee
2021-10-25 6:11 ` Nala Ginrut [this message]
2021-10-25 6:35 ` Maxime Devos
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=CAPjoZocM_R4+6q6q1RpdX+R4yNLqMX_+ZcZwgwOTqOA2YU0h9Q@mail.gmail.com \
--to=nalaginrut@gmail.com \
--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).