From: Michael Brailsford <brailsmt@...>
Date: 2003-07-01T17:48:51+09:00
Subject: Re: Swig and the STL


--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> > I am having troubles with swig's conversion of STL to ruby.  Mainly ruby
> > sees the STL containers as being empty.  Is this a know issue with swig?
> > I am running swig version 1.3.16, and ruby 1.8.0.  Does anyone know of a
> > place that I can check known issues with swig and ruby?

Just to update.  I am using swig 1.3.16, and the behavior I have noticed
is that whenever I call a .each on any vector that has been wrapped by
swig, ruby segfaults.

> I would ask this question on the SWIG mailing list.  There is some
> discussion about making the list a pseudo-members-only list so it'd be best
> to join before posting to it (not sure exactly how far these policies have
> gone yet).
> 
> Regardless, if you'll be using SWIG/Ruby it'd be beneficial to discuss
> things there.

I will take that advice.

> Personally I'm using ruby 1.7.3 and SWIG 1.3.17 with the STL without
> problem--but I've been doing custom typemaps instead of using the default
> ones (which didn't exist when I started), so that data point may not be of
> that much use to you.

I am using ruby 1.8, and swig 1.3.16.  If you don't mind could you tell
the main things to consider when writing a custom typemap for an stl
conatiner?  I have pretty much resigned myself to writing my own
typemap, and pointers from someone that has done it for std::vector
would be appreciated.

-- 
Michael
GnuPG Fingerprint:  4C56 7C23 8BD9 8B39 C4D4 B8F3 42FB 3634 31B5 E963

--Dxnq1zWXvFF0Q93v
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/AUrvQvs2NDG16WMRAhZUAKDxI+sEhLjgIq4HjYZ3cmreVMDubwCeKqVr
zue5Sg2lTnj6mTcpHzmYmp0=
=AVGy
-----END PGP SIGNATURE-----

--Dxnq1zWXvFF0Q93v--