QActiveResource is pretty cool. It looks like it might leak in the presence of Ruby exceptions, though. When I do this sort of thing, I wrap ruby.h function ca

QActiveResource is pretty cool. It looks like it might leak in the presence of Ruby exceptions, though. When I do this sort of thing, I wrap ruby.h function calls with rb_protect, check the return code, and then throw a C++ exception to unwind the stack. There is an allocation cost to doing that.