[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MIT-Scheme-devel] GTk+ in MIT-Scheme?

From: Andreas Rottmann
Subject: Re: [MIT-Scheme-devel] GTk+ in MIT-Scheme?
Date: Mon, 26 Jan 2009 19:45:26 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

address@hidden (Matt Birkholz) writes:

> Please review the Caveats (below) and the FFI Patchfile on this web
> page.
> I propose to commit that patch and thus create an FFI (a basis for an
> FFI?) for MIT Scheme.
I had a quick look, and it seems this FFI is "static" in nature;
i.e. you can not do bindings that rely on run-time data. Am I right?

> A Gtk-Screen/Canvas for Edwin in 2009 then.  Surely! ;-)
Since you mention GTK+ bindings: are you aware of
gobject-introspection[0]? It is designed to make the creating of both
static and dynamic bindings much easier, as it should be possible to
create fully-functional bindings using only the introspected data (you'd
probably add a few niceties here and there, but the effort for doing
bindings of a library there is gobject-introspection data for should be
several orders of magnitude less).

I do a (runtime) binding library based on gobject-introspection called
sbank[1] (currently for R6RS implementations that provide a FFI that
supports runtime bindings -- currently working are Ikarus and MzScheme,
but Ypsilon is in the works). If you decide to do runtime bindings
(although, if I'm right, it doesn't look like it), this could be an
opportunity for sharing code -- a large part of the sbank code could be
reused in a R5RS implementation with a bit of refactoring (which could
be done in a way that allows the same code base for use in a R6RS and
R5RS environment).


Cheers, Rotty
Andreas Rottmann         | address@hidden      | address@hidden | address@hidden     | GnuPG Key:
Fingerprint              | C38A 39C5 16D7 B69F 33A3  6993 22C8 27F7 35A9 92E7

The best way to accelerate a Windows machine is at 9.81 m/s^2

reply via email to

[Prev in Thread] Current Thread [Next in Thread]