From: Tristan Colgate <tcolgate@gmail.com>
To: swig-user@lists.sourceforge.net, guile-user@gnu.org
Subject: swig guile2
Date: Sat, 19 Mar 2011 20:08:54 +0000 [thread overview]
Message-ID: <AANLkTi=Nvyk6Lb3M96vMLi9fuOgdo+zs4prrNQm2pnc4@mail.gmail.com> (raw)
Hi All,
I'm working on a couple of projects using guile and swig and
recently did some work to put together a guile2 module for swig.
I started out by trying to add guile2 support to the existing guile
support but the focus on the old GH interface meant things started to
get messy so I've basically copied the old guile module and removed
all the legacy gh support and updated the memory management for
guile2.
It is a bit of a hack but as far as I can tell it is working OK for
me at the moment.
I thought now would be a good time to announce the effort and gauge opinion.
Guile2 has lots of nice features and I think a dedicated module
could do interesting things without breaking legacy support. Guile 2
has an FFI that could potententially be useful in the future (I like
SWIGs typemaps far too much to have moved away from swig all together
though).
The code is currently on github, and I would welcome feedback. It is
a bit rough and ready, and my knowledge of SWIG internals is pretty
rudimentary, so I'd welcome comment and advise (and patches), from all
sides.
http://github.com/tcolgate/swig-guile2
Be sure to check out the guile2 branch.
--
Tristan Colgate-McFarlane
----
"You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"
next reply other threads:[~2011-03-19 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 20:08 Tristan Colgate [this message]
2011-03-21 20:32 ` swig guile2 William S Fulton
2011-03-22 8:16 ` Tristan Colgate
2011-03-25 20:14 ` [Swig-user] " William S Fulton
2011-04-08 6:53 ` Tristan Colgate
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='AANLkTi=Nvyk6Lb3M96vMLi9fuOgdo+zs4prrNQm2pnc4@mail.gmail.com' \
--to=tcolgate@gmail.com \
--cc=guile-user@gnu.org \
--cc=swig-user@lists.sourceforge.net \
/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).