From: adriano <randomlooser@riseup.net>
To: guile-user <guile-user@gnu.org>
Subject: Re: foreign objects and the garbage collector
Date: Tue, 21 Sep 2021 16:00:52 +0200 [thread overview]
Message-ID: <5daca356c077a108d530b7a88d2361b4a0d63ce1.camel@riseup.net> (raw)
In-Reply-To: <87czp4h1un.fsf@laura>
Hi Olivier,
thank you very much for your reply
Il giorno dom, 19/09/2021 alle 14.11 -0400, Olivier Dion ha scritto:
> On Sun, 19 Sep 2021, adriano <randomlooser@riseup.net> wrote:
> >
> >
> > It'd be so nice to have an example
>
> (define (with-my-resource token proc)
> (let ((resource #f))
> (dynamic-wind
> (lambda ()
> (set! resource (open-my-resource% token)))
>
> (proc resource)
>
> (lambda ()
> (when resource
> (close-my-resource% resource))))))
>
> (with-my-resource "some-internal-token" (lambda ()))
Oh my, thank you for this !
This should be included in the manual !
The example that's there currently is totally indequate, in my opinion
> >
>
> Says you have `open_my_resource()` and `close_my_resource()` in C in
> library "libfoo.so" where open_my_resource takes a C string and returns
> an integer for the resource while close_my_resource takes the integer
> of
> the resource:
>
> (define open-my-resource%
> (eval-when (eval load compile)
> (let ((this-lib (load-foreign-library "libfoo")))
> (foreign-library-function this-lib "open_my_resource"
> #:return-type int
> #:arg-types (list '*))))
>
> (define open-my-resource%
> (eval-when (eval load compile)
> (let ((this-lib (load-foreign-library "libfoo")))
> (foreign-library-function this-lib "open_my_resource"
> #:return-type int
> #:arg-types (list int)))))
Uhmm... I see 2 versions of open-my-resource%
The only slight difference I see is in the #:arg-types
The first one has
(list '*)
and the second one has
(list int)
Maybe you you got confused while editing ?
This would be my version of close-my-resource%
(define close-my-resource%
(eval-when (eval load compile)
(let ((this-lib (load-foreign-library "libfoo")))
(foreign-library-function this-lib "close_my_resource"
#:return-type int
#:arg-types (int)))))
>
> Note that you probably need to do a wrapper named `open-my-resource`
> to
> do the conversion of scm_string to C raw pointer before calling
> `open-my-resource%` in this particular case.
Ok
>
> This is just an example, but it shows you that you can call foreign C
> primitives easily without any C code, and that you have to use a
> dynamic context to manage the lifetime of the C resources.
>
Thank you again
next prev parent reply other threads:[~2021-09-21 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 12:41 foreign objects and the garbage collector Tim Meehan
2021-09-04 13:35 ` Vivien Kraus via General Guile related discussions
2021-09-05 0:58 ` Tim Meehan
2021-09-19 6:14 ` adriano
2021-09-19 18:11 ` Olivier Dion via General Guile related discussions
2021-09-19 18:23 ` Maxime Devos
2021-09-21 14:26 ` adriano
2021-09-21 18:49 ` Maxime Devos
2021-09-21 14:00 ` adriano [this message]
2021-09-21 14:25 ` Olivier Dion via General Guile related discussions
2021-09-21 14:51 ` adriano
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=5daca356c077a108d530b7a88d2361b4a0d63ce1.camel@riseup.net \
--to=randomlooser@riseup.net \
--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).