From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: Dmitry Bogatov <KAction@gnu.org>
Cc: guile-devel@gnu.org, Amirouche Boubekki <amirouche@hypermove.net>
Subject: Re: [PATCH 18/25] write documentation for (system foreign declarative)
Date: Tue, 19 Jul 2016 16:41:21 +0200 [thread overview]
Message-ID: <87mvldwuzy.fsf@T420.taylan> (raw)
In-Reply-To: <E1bPEsh-0000m9-Ti@eggs.gnu.org> (Dmitry Bogatov's message of "Mon, 18 Jul 2016 23:11:04 +0300")
Dmitry Bogatov <KAction@gnu.org> writes:
> [2016-07-18 21:41] Amirouche Boubekki <amirouche@hypermove.net>
>>
>> On 2016-07-18 17:17, KAction@gnu.org wrote:
>> > From: Dmitry Bogatov <KAction@gnu.org>
>> >
>> > Document '<foreign-type>' record type and 'define-foreign-type'
>> > procedure.
>>
>> Can you compare this 'foreign-type' library with scheme-bytestructures [0].
>> How can both libraries help each other? Work hand in hand?
>
> Seems that 'scheme-bytestructures' can be used to implement something like
> `define-foreign-struct', but since it is not currently part of Guile, I, sure,
> can't depend on it.
>
> Also, 'parse-c-struct' provides similiar functionality.
I was keeping an eye on this thread because it sounded like something
bytestructures could help in. Tell me if you need cooperation; I'm the
author of bytestructures.
I'm not sure if the Guile maintainers would like to make bytestructures
a part of Guile as it stands, but I have my FSF copyright assignment
paperwork done and from my side all is fine. John Cowan wants to make
it a SRFI for possible adoption in R7RS-large, which would have some
implications on future design and implementation choices in the project
(e.g. not making it dependent on any Guile-specific concepts) but I'll
prioritize Guile if I'm forced to make choices.
Taylan
next prev parent reply other threads:[~2016-07-19 14:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 15:17 Foreign-declarative module KAction
2016-07-18 15:17 ` [PATCH 01/25] New module: system/foreign/declarative.scm KAction
2016-07-18 15:17 ` [PATCH 02/25] Define <ffi-type> structure KAction
2016-07-18 17:41 ` Nala Ginrut
2016-07-18 17:59 ` Dmitry Bogatov
2017-03-10 4:46 ` Thien-Thi Nguyen
2017-03-12 6:00 ` Dmitry Bogatov
2016-07-18 15:17 ` [PATCH 03/25] Mirror types from system/foreign as <foreign-type> KAction
2016-07-18 15:17 ` [PATCH 04/25] Write boilerplate for primitive types KAction
2016-07-18 15:17 ` [PATCH 05/25] Fix bug in `default' macro KAction
2016-07-18 15:17 ` [PATCH 06/25] Basic implementation of `define-foreign-function' KAction
2016-07-18 15:17 ` [PATCH 07/25] Introduce foreign-type predicates KAction
2016-07-18 15:17 ` [PATCH 08/25] Add keywords for `define-foreign-function' macro KAction
2016-07-18 15:17 ` [PATCH 09/25] system/foreign/declarative: rename `predicate' to `validate' KAction
2016-07-18 15:17 ` [PATCH 10/25] Refactor type validation in `define-foreign-function' KAction
2016-07-18 15:17 ` [PATCH 11/25] system/foreign/declarative: new macro KAction
2016-07-18 15:17 ` [PATCH 12/25] Improve deriving c symbol name from scheme one KAction
2016-07-18 15:17 ` [PATCH 13/25] system/foreign/declarative.scm: export string foreign type KAction
2016-07-18 15:17 ` [PATCH 14/25] foreign/declarative: mirror more primitive types KAction
2016-07-18 15:17 ` [PATCH 15/25] New macro: with-pointer KAction
2016-07-18 15:17 ` [PATCH 16/25] Configure emacs file-local indention KAction
2016-07-18 15:17 ` [PATCH 17/25] system/foreign/declarative: unexport internal macro KAction
2016-07-18 15:17 ` [PATCH 18/25] write documentation for (system foreign declarative) KAction
2016-07-18 19:41 ` Amirouche Boubekki
2016-07-18 20:11 ` Dmitry Bogatov
2016-07-19 14:41 ` Taylan Ulrich Bayırlı/Kammer [this message]
2016-07-19 15:12 ` Dmitry Bogatov
2016-07-18 15:17 ` [PATCH 19/25] Document define-foreign-bitmask macro KAction
2016-07-18 15:17 ` [PATCH 20/25] Document with-pointer macro KAction
2016-07-18 15:17 ` [PATCH 21/25] new module: (ice-9 xattr) KAction
2016-07-18 15:17 ` [PATCH 22/25] ice-9/xattr: implement `xattr-get' function KAction
2016-07-18 15:17 ` [PATCH 23/25] Do not throw exception on missing xattr KAction
2016-07-18 15:17 ` [PATCH 24/25] Refactor defining foreign libattr function KAction
2016-07-18 15:17 ` [PATCH 25/25] ice9/attr: implement xattr-list procedure KAction
2017-03-09 20:33 ` Andy Wingo
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=87mvldwuzy.fsf@T420.taylan \
--to=taylanbayirli@gmail.com \
--cc=KAction@gnu.org \
--cc=amirouche@hypermove.net \
--cc=guile-devel@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).