From: Catonano <catonano@gmail.com>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: a foreign struct: a shameless request
Date: Sun, 18 Jun 2017 08:22:15 +0200 [thread overview]
Message-ID: <CAJ98PDxn-Z4kbwsUgpqm9KqB+9gd-rpA_WEWv_ZUU7eGtcaO0w@mail.gmail.com> (raw)
In-Reply-To: <87wp8bsqmn.fsf@gmail.com>
Taylan,
2017-06-16 21:02 GMT+02:00 Taylan Ulrich Bayırlı/Kammer <
taylanbayirli@gmail.com>:
>
>
> If you decide to use bytestructures, feel free to e-mail me privately or
> use the GitHub issues system for questions. I don't actively monitor
> the Guile ML these days so I may miss your questions and feedback here.
>
> [0] https://github.com/TaylanUB/scheme-bytestructures/
>
>
Than you for your offer !
I am impressed that Bytestructures works on so many different scheme
implementations
I am a bit concerned that it as no proper packaging so it'd be hard to port
it in Guix. That's an issue for me
I took a look at the code, though
I think I understand now
The size of the union'ed field has to be the maximum of the sizes of the
types of the things the field could be populated with
That's all I need, I think, to use make-c-struct
Then I can pass the thing to Ffreexl functions and they will populate it
Then, depending on the contents of the type field, I can parse the thing
accordingly, to get back scheme things
This is the master plan
I can't do it today, though. I'll be busy
I'll get back to you, with this
Thanks for showing me scheme-bytestructures !
next prev parent reply other threads:[~2017-06-18 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 16:04 a foreign struct: a shameless request Catonano
2017-06-16 19:02 ` Taylan Ulrich Bayırlı/Kammer
2017-06-18 6:22 ` Catonano [this message]
2017-06-18 12:28 ` Amirouche
2017-06-18 14:41 ` 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=CAJ98PDxn-Z4kbwsUgpqm9KqB+9gd-rpA_WEWv_ZUU7eGtcaO0w@mail.gmail.com \
--to=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=taylanbayirli@gmail.com \
/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).