From: Tristan Colgate <tcolgate@gmail.com>
To: William S Fulton <wsf@fultondesigns.co.uk>
Cc: guile-user@gnu.org, swig-user@lists.sourceforge.net,
Matthias Koeppe <mkoeppe+swig@mail.math.uni-magdeburg.de>
Subject: Re: swig guile2
Date: Tue, 22 Mar 2011 08:16:03 +0000 [thread overview]
Message-ID: <AANLkTi=oZypyrURcACCH7PBisHrs-LC+LBvhjOzZrjcD@mail.gmail.com> (raw)
In-Reply-To: <4D87B5D2.5040800@fultondesigns.co.uk>
On 21 March 2011 20:32, William S Fulton <wsf@fultondesigns.co.uk> wrote:
> Are you proposing a 2nd SWIG Guile module in addition to the current module?
The code as it stands is exactly that, a new module. I have worked
under the assumption that breaking the existing guile support was
taboo.
> I am no guile user, so can't help on the Guile side. The guile SWIG module
> is suffering neglect and doesn't seem to work with modern versions of Guile
> - the test-suite fails for me. Only very rarely are there Guile queries on
> the SWIG mailing list, so suspect it isn't used much. Would it make sense to
> drop the older Guile interface altogether and just use Guile 2?
The existing guile module support the gh_ interface and the older
version of the SCM interface. It also doesn't work with guiles current
GC. It's entirely useless for the current version of guile. I had
assumed that since SWIG still ships it, enough people care about
legacy guile support to not want it broken.
I've only just started looking into getting the test-suite working
with my guile2 work, but I do intend on getting it to the point where
it all passes.
For me personally, the old guile module is no longer useful.
However, guile 2.0 is not widely deployed in distributions yet and
that may take some time.
> BTW, there
> is the swig -scm option for guile 1.6+. So there seems to be GH and SCM and
> now guile 2 API... does that sound right that there are so many C interfaces
> or is your Guile 2 interface just SCM?
The -scm support works by mapping the old SCM interface to the GH
interface.. Almost all the scm_ calls used by the existing guile
module are deprecated. I tried implementing and -scm2 option within
the existing module but it was more awkward than I could bare.
I'm not sure that there is going to be enormous support for this
within the guile community either really. Guile 2 ships with a new FFI
and using that is, obviosuly, of more interest to them. I've struggled
wrapping legacy APIs with it though and SWIG really is rather good.
--
Tristan Colgate-McFarlane
----
"You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
next prev parent reply other threads:[~2011-03-22 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 20:08 swig guile2 Tristan Colgate
2011-03-21 20:32 ` William S Fulton
2011-03-22 8:16 ` Tristan Colgate [this message]
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=oZypyrURcACCH7PBisHrs-LC+LBvhjOzZrjcD@mail.gmail.com' \
--to=tcolgate@gmail.com \
--cc=guile-user@gnu.org \
--cc=mkoeppe+swig@mail.math.uni-magdeburg.de \
--cc=swig-user@lists.sourceforge.net \
--cc=wsf@fultondesigns.co.uk \
/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).