From: ludo@gnu.org (Ludovic Courtès)
To: taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer")
Cc: guile-user@gnu.org
Subject: Re: Bytestructures, FFI
Date: Thu, 02 Jun 2016 09:04:54 +0200 [thread overview]
Message-ID: <87eg8gax61.fsf@gnu.org> (raw)
In-Reply-To: <87y46oa1xm.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Thu, 02 Jun 2016 03:07:17 +0300")
Hi,
taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> I'll try to grok your approach later and see how it compares, but let me
> mention that the syntax-case based macro API of bytestructures lets one
> hoist all computation to macro-expand time:
Ah, very nice!
Ludo’.
prev parent reply other threads:[~2016-06-02 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 19:29 Bytestructures, FFI Taylan Ulrich Bayırlı/Kammer
2016-05-31 20:13 ` Amirouche Boubekki
2016-05-31 21:07 ` Taylan Ulrich Bayırlı/Kammer
2016-06-01 21:40 ` Ludovic Courtès
2016-06-02 0:07 ` Taylan Ulrich Bayırlı/Kammer
2016-06-02 7:04 ` Ludovic Courtès [this message]
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=87eg8gax61.fsf@gnu.org \
--to=ludo@gnu.org \
--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).