From: Leon Henrik Plickat <leonhenrik.plickat@stud.uni-goettingen.de>
To: 宋文武 <iyzsong@envs.net>
Cc: <guile-user@gnu.org>
Subject: Re: Calling user defined guile functions from C?
Date: Sun, 26 Nov 2023 10:07:59 +0100 [thread overview]
Message-ID: <CX8MIN6L192F.3C4IQWEV99SIP@stud.uni-goettingen.de> (raw)
In-Reply-To: <87msv3o274.fsf@envs.net>
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
Thank you! With your input this was mostly straight-forward.
I'll leave the repository link here, should anyone else wanting to do
something similar stumbles uppon this exchange:
https://git.sr.ht/~leon_plickat/riverguile/
--
Friendly greetings,
Leon Henrik Plickat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-11-26 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:53 Calling user defined guile functions from C? Leon Henrik Plickat
2023-11-24 10:50 ` 宋文武
2023-11-26 9:07 ` Leon Henrik Plickat [this message]
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=CX8MIN6L192F.3C4IQWEV99SIP@stud.uni-goettingen.de \
--to=leonhenrik.plickat@stud.uni-goettingen.de \
--cc=guile-user@gnu.org \
--cc=iyzsong@envs.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 read-only IMAP folder(s) and NNTP newsgroup(s).