[Insight-users] Re: SWIG 1.3.22 in CableSwig?

[Gaetan Lehmann]

Hi,

The old version of SWIG included in cableswig becomes more and more a  
problem.
Python 2.5 for example have changed the signature of some functions, so we  
now have to use the -fpermissive option to be able to build WrapITK with  
that python release.
Cableswig can't stay with an old release of SWIG too much time. It now  
becomes a real problem.
I know that the long term way to go is to drop cableswig and to implement  
an xml parser in swig to parse gccxml output, but nobody seems to be ready  
to do that for now, so wouldn't it be a good idea to update the SWIG  
version of cableswig untill someone found enough time to implement the  
swig parser ?

Regards,

Gaetan


On Wed, 09 Aug 2006 22:36:32 +0200, Charl P. Botha <cpbotha at cpbotha.net>  
wrote:

> Dear CableSwig developers (mostly Brad!)
>
> Are there any plans to upgrade CableSwig to SWIG 1.3.22?  As far as I
> can make out, it's currently synced with 1.3.21.
>
> At the moment, although a vector<basic_string<char> > is essentially
> the same as a vector<string>, and Swig 1.3.22 recognises it as such,
> WrapITK cannot correctly show return values of methods that return
> vectors of strings, for example GDCMSeriesFilenames::GetFileNames and
> GetSeriesUIDs.    I'm especially interesting in the std::string (and
> basic_string<char> vs. string equivalency) mentioned in the changelog
> at  
> http://sourceforge.net/project/shownotes.php?release_id=265569&group_id=1645
> (search for 'basic_string')
>
> Thanks for any info,
> Charl



-- 
Gaëtan Lehmann
Biologie du Développement et de la Reproduction
INRA de Jouy-en-Josas (France)
tel: +33 1 34 65 29 66    fax: 01 34 65 29 09
http://voxel.jouy.inra.fr