From: Chris Vine <vine35792468@gmail.com>
To: guile-user@gnu.org
Subject: Re: segmenation fault
Date: Fri, 9 Jun 2017 12:18:34 +0100 [thread overview]
Message-ID: <20170609121834.1eae7cf7@dell.homenet> (raw)
In-Reply-To: <CAJ98PDyiMyVmgtxz_SjmTjx3-05VK4J9P-BorqT+rHn-9bq8qg@mail.gmail.com>
On Fri, 9 Jun 2017 10:17:18 +0200
Catonano <catonano@gmail.com> wrote:
> 2017-06-09 10:00 GMT+02:00 Amirouche Boubekki
> <amirouche.boubekki@gmail.com> :
>
> > It's something like (bytevector->pointer (make-vector)) there is a
> > make-double-pointer procedure in guile git
>
> Thank you !!
>
> I took a look at the guile-gcrypt code and I found
>
> (bytevector->pointer (make-bytevector (sizeof '*))
>
> I was going to write this right now !
>
> It works !
> I just called freexl-open and it returned 0 !!
If you want to manipulate a scheme bytevector at the C level you can
also look at the c-write procedure here for ideas:
https://github.com/ChrisVine/guile-a-sync/blob/master/lib/unix_write.c
(As a point of detail, this procedure is only required with guile-2.0 -
with guile-2.2, suspendable ports are used instead - but it shows you
one approach to working with scheme buffers or other objects.)
Chris
next prev parent reply other threads:[~2017-06-09 11:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 7:21 segmenation fault Catonano
2017-06-09 7:43 ` Thomas Danckaert
2017-06-09 8:00 ` Amirouche Boubekki
2017-06-09 8:17 ` Catonano
2017-06-09 11:18 ` Chris Vine [this message]
2017-06-09 16:36 ` Josh Datko
2017-06-09 20:18 ` Catonano
2017-06-11 20:56 ` Catonano
2017-06-11 22:09 ` Catonano
2017-06-09 8:42 ` Catonano
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=20170609121834.1eae7cf7@dell.homenet \
--to=vine35792468@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).