From: Mike Gran <spk121@yahoo.com>
To: Amirouche <amirouche@hypermove.net>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: How to make GNU Guile more successful
Date: Fri, 3 Mar 2017 19:24:29 +0000 (UTC) [thread overview]
Message-ID: <302221832.550562.1488569069023@mail.yahoo.com> (raw)
In-Reply-To: <baed7f54-c4d8-c7f2-9d38-ccc1fc787b5d@hypermove.net>
> On Friday, March 3, 2017 11:18 AM, Amirouche <amirouche@hypermove.net> wrote:
>> Now that the C preprocessor in NYACC/C99 is more robust I could start looking at generating some sort of “FFI helper” functionality. I have been thinking about this problem on and off for a while. Completely automating things might be tough, but a “helper” would probably go a long way.
> Are you aware of scheme-bytestructures [0] that's what we are using> in guile-git. If you target that API to wrap C structs, it would be helpful.
SWIG used to work for Guile. It was a rather complete solution to
the wrapping problem.
next prev parent reply other threads:[~2017-03-03 19:24 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 6:05 How to make GNU Guile more successful Michael Vehrs
2017-02-20 20:41 ` Arne Babenhauserheide
2017-02-21 6:01 ` Michael Vehrs
2017-02-21 17:18 ` Arne Babenhauserheide
2017-02-21 18:19 ` Amirouche
2017-02-21 18:31 ` Mike Gran
2017-02-21 18:33 ` Amirouche
2017-02-21 18:41 ` Mike Gran
2017-02-21 18:15 ` Amirouche
2017-02-21 19:25 ` Arne Babenhauserheide
2017-03-01 19:25 ` Amirouche
2017-03-03 5:28 ` Nala Ginrut
2017-03-03 9:18 ` David Kastrup
2017-03-03 11:30 ` Nala Ginrut
2017-03-03 12:19 ` David Kastrup
2017-03-03 13:35 ` Nala Ginrut
2017-03-04 23:44 ` Arne Babenhauserheide
2017-03-05 2:05 ` Thomas Morley
2017-03-05 14:01 ` Thomas Morley
2017-03-05 14:09 ` David Kastrup
2017-03-05 14:13 ` Thomas Morley
2017-03-05 14:27 ` Thomas Morley
2017-03-06 20:41 ` Lilypond speed (was Re: How to make GNU Guile more successful) Andy Wingo
2017-03-08 23:17 ` Thomas Morley
2017-03-08 23:50 ` David Kastrup
2017-03-09 6:48 ` Thien-Thi Nguyen
2017-03-09 12:13 ` Ludovic Courtès
2017-03-09 13:28 ` Paul
2017-03-10 16:18 ` Ludovic Courtès
2017-03-10 18:53 ` Paul
2017-03-12 21:07 ` Thomas Morley
2017-03-12 21:42 ` Ludovic Courtès
2017-03-12 23:20 ` Matt Wette
2017-03-13 12:52 ` Andy Wingo
2017-03-13 14:10 ` Controlling optimizations in 2.2 Ludovic Courtès
2017-03-13 21:26 ` Andy Wingo
2017-03-03 17:21 ` How to make GNU Guile more successful Matt Wette
2017-03-03 19:09 ` Amirouche
2017-03-03 19:16 ` Amirouche
2017-03-03 19:24 ` Mike Gran [this message]
2017-03-03 20:10 ` Matt Wette
2017-03-03 20:09 ` Matt Wette
2017-02-22 5:51 ` Michael Vehrs
-- strict thread matches above, loose matches on Subject: below --
2017-03-10 2:08 Vítor De Araújo
2017-03-10 9:55 ` Arne Babenhauserheide
2017-03-10 10:03 ` Panicz Maciej Godek
2017-03-10 14:27 ` vbuaraujo
2017-03-10 15:08 ` Panicz Maciej Godek
2017-03-11 7:19 ` Thien-Thi Nguyen
2017-03-13 15:55 ` Nala Ginrut
2017-03-13 16:14 ` Panicz Maciej Godek
2017-03-10 20:17 ` Amirouche
2017-03-11 0:50 ` Vítor De Araújo
2017-03-11 3:02 ` Vítor De Araújo
2017-03-11 7:42 ` Thien-Thi Nguyen
2017-03-14 3:26 ` Christopher Allan Webber
2017-03-04 23:41 Alejandro Sanchez
2017-03-05 0:23 ` Arne Babenhauserheide
2017-03-05 8:23 ` Thien-Thi Nguyen
2017-03-05 14:19 ` Arne Babenhauserheide
2017-03-05 3:09 ` Erik Edrosa
2017-03-05 11:57 ` Jan Wedekind
2017-03-07 3:29 ` Erik Edrosa
2017-03-05 14:27 ` Arne Babenhauserheide
2017-03-05 16:43 ` Nala Ginrut
2017-03-05 23:46 ` Alejandro Sanchez
2017-03-06 9:00 ` Arne Babenhauserheide
2017-03-06 1:31 ` Matt Wette
2017-03-07 4:07 ` Erik Edrosa
2017-03-05 9:40 ` David Kastrup
2017-02-18 1:04 sirgazil
[not found] ` <6315ebf51aec83aaff1c7fbbec685c0b@openmailbox.org>
2017-02-18 15:29 ` sirgazil
2017-02-18 16:55 ` David Pirotte
2017-02-19 18:09 ` sirgazil
2017-02-20 1:00 ` David Pirotte
2017-02-12 23:56 Amirouche
2017-02-13 0:21 ` Amirouche
2017-02-13 11:06 ` Arne Babenhauserheide
2017-02-13 12:14 ` Arne Babenhauserheide
2017-02-13 20:20 ` Amirouche
2017-02-13 23:08 ` Arne Babenhauserheide
2017-02-13 20:28 ` Panicz Maciej Godek
2017-02-13 20:42 ` Amirouche
2017-02-13 22:34 ` Marko Rauhamaa
2017-02-13 23:56 ` Arne Babenhauserheide
2017-02-14 0:18 ` David Kastrup
2017-02-14 22:21 ` Arne Babenhauserheide
2017-02-15 17:03 ` Christopher Allan Webber
2017-02-16 19:18 ` sirgazil
2017-02-16 20:26 ` Amirouche
2017-02-14 5:59 ` Marko Rauhamaa
2017-02-14 19:36 ` Linas Vepstas
2017-02-14 20:54 ` Marko Rauhamaa
2017-02-14 22:20 ` Arne Babenhauserheide
2017-02-13 22:54 ` Arne Babenhauserheide
2017-02-14 9:54 ` Panicz Maciej Godek
2017-02-14 21:35 ` Arne Babenhauserheide
2017-03-01 19:21 ` Amirouche
2017-03-10 20:23 ` Amirouche
2017-07-14 21:54 ` Linas Vepstas
2017-07-14 21:59 ` Marko Rauhamaa
2017-07-15 10:10 ` Jan Wedekind
2017-07-15 12:55 ` Nala Ginrut
2017-07-15 12:58 ` Nala Ginrut
2017-07-15 22:17 ` Jan Wedekind
2017-07-16 9:54 ` Nala Ginrut
2017-07-17 18:52 ` Arun Isaac
2017-07-18 11:22 ` Ernest Adrogué
2017-07-16 8:30 ` Freja Nordsiek
2017-07-16 9:18 ` Marko Rauhamaa
2017-07-16 10:11 ` Freja Nordsiek
2017-07-16 10:31 ` Marko Rauhamaa
2017-07-16 10:39 ` Freja Nordsiek
2017-07-16 10:45 ` Freja Nordsiek
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=302221832.550562.1488569069023@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=amirouche@hypermove.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).