[Swig-devel] [ swig-Patches-1511038 ] [guile] guile module uses deprecated interfaces

[SourceForge.net <no...@so...>]

Patches item #1511038, was opened at 2006-06-22 18:50
Message generated for change (Comment added) made by gjanssens
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301645&aid=1511038&group_id=1645

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: general
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Aaron VanDevender (dotsig)
Assigned to: Matthias Koeppe (mkoeppe)
Summary: [guile] guile module uses deprecated interfaces

Initial Comment:
During the 1.7 development branch of guile, a lot of
the API changed, especially with regaurd to memory
allocation /garbage colleciton, and string
representation. SWIG currently supports only the 1.6
style API, but now that guile has stabilized and 1.8 is
released, we need to update to the new interface. This
patch does that.

----------------------------------------------------------------------

Comment By: Geert Janssens (gjanssens)
Date: 2011-12-30 03:01

Message:
Adam Tkac from Fedora created a patch on the Fedora bugreport
(https://bugzilla.redhat.com/show_bug.cgi?id=704527) for this issue:
https://bugzilla.redhat.com/attachment.cgi?id=533764&action=diff

Can you give some feedback on whether this would be acceptable for upstream
inclusion ?

----------------------------------------------------------------------

Comment By: Geert Janssens (gjanssens)
Date: 2011-11-08 04:42

Message:
The last comment on this bug is now more than 4 years old. Meanwhile guile
has released version 2.0 and the impact of using deprecated functions has
changed slightly. With guile 2.0, the wrappers fail to work as they are
now.

I'm a maintainer of the gnucash project, which heavily depends on the guile
bindings swig generates and we're getting more and more bug reports about
this problem. I'll add some links to show what I mean:
* https://bugzilla.redhat.com/show_bug.cgi?id=704527
* https://bugzilla.redhat.com/show_bug.cgi?id=706140
* https://bugzilla.gnome.org/show_bug.cgi?id=655901

So the problem reported here seems to have more impact on guile 2.0 than it
had on 1.8.

----------------------------------------------------------------------

Comment By: Olly Betts (olly)
Date: 2007-10-23 07:32

Message:
Logged In: YES 
user_id=14972
Originator: NO

Matthias Koeppe (SWIG's guile maintainer) made some comments on this issue
on the swig-dev mailing list, which I'm pasting below for the record.  The
full message is here:

http://article.gmane.org/gmane.comp.programming.swig.devel/17577

His comments:

Basically, current SWIG does support Guile 1.8 perfectly as far as I
know, though it might use some deprecated functions.  At this point of
time, I will not apply patches if they break compatibility with Guile
1.6 (not sure if "swig -guile -scm" still supports Guile 1.4, though)
purely for the sake of fixing deprecation warnings.

I fully agree with your comment, Olly, on the bug tracker item.  A
patch that uses wrapper-compile-time conditionalization (rather than
SWIG-configure-time conditionalization as the submitted patch) on the
Guile version to avoid using deprecated interfaces on Guile 1.8 could
be easily accepted and merged.

----------------------------------------------------------------------

Comment By: Olly Betts (olly)
Date: 2007-09-17 17:11

Message:
Logged In: YES 
user_id=14972
Originator: NO

I just had a quick look at this patch.  Guile isn't my area of expertise at
all, but I don't think we have an active guile maintainer currently and
this patch has languished for over a year.

I see one major issue with it - you're performing a configure time check
for functions provided by guile, but in SWIG configure probing should only
be to used to find interpreters to run tests with, and to detect functions,
etc which for building SWIG itself.

It should be possible to use SWIG to generate wrappers without even having
guile installed (though obviously you can't build them, but you can ship
them in a tarball with your library for example).  And ideally the wrappers
SWIG generates should be buildable against any supported version of guile,
for example if guile's C header provides a "GUILE_VERSION" define, check
this to see which functions to use.  Where this isn't possible SWIG
sometimes provides a command line option to select what version to generate
for.  Or you could allow the compiling user to set a C preprocessor define
to enable support for a particular version, defaulting to 1.8 if that's
most popular.  If 1.6 just isn't of interest to users now (I really have no
idea) then supporting 1.8 only might be a reasonable approach.


----------------------------------------------------------------------

Comment By: Olly Betts (olly)
Date: 2006-09-25 18:07

Message:
Logged In: YES 
user_id=14972

Moving to the patch tracker...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301645&aid=1511038&group_id=1645