On Fri, Jan 23, 2015 at 03:25:33PM -0500, Rafael Schloming wrote: > On Fri, Jan 23, 2015 at 2:08 PM, Darryl L. Pierce <[email protected]> > wrote: > > > On Fri, Jan 23, 2015 at 01:49:34PM -0500, Rafael Schloming wrote: > > > It does talk about what swig does, but it also talks about the other > > > direction: > > > > > > "If the C structure references other ruby objects, then the mark function > > > pointer must also be provided and must properly mark the other objects > > with > > > rb_gc_mark()" > > > > What I meant is it's not showing how to do that. Swig is the one that's > > generating that Ruby struct wrapping, but I haven't found (yet) if they > > expose to users a way to tap into that adn do what we want. > > > > If you can find a way for swig to let you control it that's great, but I > was thinking we could just wrap this one struct by hand. It shouldn't be a > whole lot of code for just that struct, and swig can still handle the rest > of them.
+1 Though, I was hoping we could avoid having to manually do things... -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgpX0na7kqfSD.pgp
Description: PGP signature
