unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
To: guile-devel@gnu.org
Subject: Re: Guile Summer of Code project
Date: Thu, 27 Mar 2008 18:36:54 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803271833160.8986@ttleush> (raw)
In-Reply-To: <cmu-lmtpd-30052-1206637626-0@mail-imap1.uio.no>


Ludovic Court?s:
>>    Therefore, being able to parse and access C code from Scheme/Guile itself,
>>    and handling such a code like any other Scheme object would clearly
>>    benefit the community opening many new possibilities.
>>
>>    For example, creating Guile bindings through a foreign function generator
>>    using the parser on headers for popular C libraries and applications
>>    would be plain easy.
>
> Again, I'm not convinced that such a tool would suffice to make FFI
> generation "plain easy".
>

One project who actually makes this conversion "plain easy", is jsext:
   http://www.thescripts.com/forum/thread528081.html
jsext is a library for javascript which automatically creates wrappers
on the fly out of c header files. I know it works, because I once got
a personal demonstration from the author of it. :-) Might be worth looking
at as well.





       reply	other threads:[~2008-03-27 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cmu-lmtpd-30052-1206637626-0@mail-imap1.uio.no>
2008-03-27 17:36 ` Kjetil S. Matheussen [this message]
2008-03-27 17:57   ` Guile Summer of Code project Kjetil S. Matheussen
     [not found] <cmu-lmtpd-31700-1206464752-1@mail-imap1.uio.no>
2008-03-25 17:19 ` Kjetil S. Matheussen
2008-03-25 17:47   ` Kjetil S. Matheussen
2008-03-25 21:45     ` Neil Jerram
2008-03-20 10:12 Luis Araujo
2008-03-24 23:40 ` Neil Jerram
2008-03-26 20:52 ` Ludovic Courtès

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=Pine.LNX.4.64.0803271833160.8986@ttleush \
    --to=k.s.matheussen@notam02.no \
    --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).