M
Michael Brailsford
--pvezYHf7grwyp3Bc
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?
--
Michael
GnuPG Fingerprint: 4C56 7C23 8BD9 8B39 C4D4 B8F3 42FB 3634 31B5 E963
--pvezYHf7grwyp3Bc
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+/fWpQvs2NDG16WMRAhEmAJ9qQLDrl3V1Uyq9dlIA0CXtKZ4cIACgvF9h
vDje27uXw/SxU5HY1F4lpeo=
=kTER
-----END PGP SIGNATURE-----
--pvezYHf7grwyp3Bc--
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?
--
Michael
GnuPG Fingerprint: 4C56 7C23 8BD9 8B39 C4D4 B8F3 42FB 3634 31B5 E963
--pvezYHf7grwyp3Bc
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+/fWpQvs2NDG16WMRAhEmAJ9qQLDrl3V1Uyq9dlIA0CXtKZ4cIACgvF9h
vDje27uXw/SxU5HY1F4lpeo=
=kTER
-----END PGP SIGNATURE-----
--pvezYHf7grwyp3Bc--