From: Leon Henrik Plickat <leonhenrik.plickat@stud.uni-goettingen.de>
To: <guile-user@gnu.org>
Subject: Calling user defined guile functions from C?
Date: Thu, 23 Nov 2023 15:53:06 +0100 [thread overview]
Message-ID: <CX69Z8VEXGGC.2O6N6Y5K4NF6N@stud.uni-goettingen.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
I intend on using guile as a scripting language in a C program (a
Wayland client in this case). All documentation and tutorials I have
found focus on extending guile with C code, however I explicitly want
to drive the code from C.
What I ideally want to do is to eval a guile script on startup of the
program in which a user can define a function. The script basically
functions as configuration. Afterwards, enter the main loop and in
response to certain events call the function defined by the user
(with scm_c_eval_string("(name-of-function)") I suppose) and use its
return value (a list of lists containg 4 integers each) to respond to
the event.
Must the program run in guile mode the entire time, or can I enter
it only temporarily for eval'ing the script and calling the function?
What is the canonical way of eval'ing a script to get a function
definition from C?
Can I check after eval'ing the script whether the function I want the
user to define exists? Probably with scm_c_eval_string() again, but
I wonder if there is some other more way that is considered to be
better.
I am working my way through the API reference, but decided to ask
for some input in the meantime.
Friendly greetings,
Leon Henrik Plickat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-11-23 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:53 Leon Henrik Plickat [this message]
2023-11-24 10:50 ` Calling user defined guile functions from C? 宋文武
2023-11-26 9:07 ` Leon Henrik Plickat
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=CX69Z8VEXGGC.2O6N6Y5K4NF6N@stud.uni-goettingen.de \
--to=leonhenrik.plickat@stud.uni-goettingen.de \
--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).