From: randomlooser <randomlooser@riseup.net>
To: Tim Meehan <btmeehan@gmail.com>, guile-user@gnu.org
Subject: Re: getting to know the FFI ...
Date: Sat, 21 Nov 2020 11:19:21 +0100 [thread overview]
Message-ID: <596f1b4be569e76f2bc70bfd9994b2228d019025.camel@riseup.net> (raw)
In-Reply-To: <CACgrOxJZKxE4eL9keY5HBmqnT9yA22VOrq3Hn2RLd=BsE2PJgQ@mail.gmail.com>
Il giorno gio, 19/11/2020 alle 21.02 -0600, Tim Meehan ha scritto:
> I figured that I would try and do something simple-ish to see how
> well I
> understood the FFI. I found this GTK tutorial, written in Chez
> Scheme:
> https://github.com/jhidding/lyonesse/blob/master/gtk-tutorial/window.scm
> I just tried to replace the Chez FFI calls with Guile FFI calls.
>
> I'm not sure how to tell GTK about a callback that is written in
> Guile.
> I'm not sure how to pass a string to GTK ...
>
> Cheers,
> My bug-ridden source follows:
I'm not sure I understand
Are you asking for a review of your code ?
Did you run this code ?
next prev parent reply other threads:[~2020-11-21 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 3:02 getting to know the FFI Tim Meehan
2020-11-21 10:19 ` randomlooser [this message]
2020-11-22 14:55 ` Matt Wette
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=596f1b4be569e76f2bc70bfd9994b2228d019025.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=btmeehan@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).