On Fri, Feb 06, 2015 at 08:37:07AM -0500, Rafael Schloming wrote:
Is this the approach you referenced in your other email? (Same request here
for a pointer to the highlighted key bits of the approach.)
No, this was a third approach to the problem, since we can't directly
affect the object
Is this the approach you referenced in your other email? (Same request here
for a pointer to the highlighted key bits of the approach.)
On Fri, Jan 30, 2015 at 4:11 PM, Darryl L. Pierce dpie...@redhat.com
wrote:
So over the last week I've been working on a way to avoid leaking memory
or
So over the last week I've been working on a way to avoid leaking memory
or causing segfaults when the underlying C library is giving a reference
to a Ruby object. And after much coding and gnashing of teeth I foudn
the easiest way to do this with manually wrapping the pn_record_t
struct. That
