[Kde-bindings] QtRuby memleak continued

[Caleb Tennis]

> I think the QtRuby code for QStrings is probably wrong, but for 'char *'s
> I'm
> not sure as there are no rules for who 'owns' the string after the call
> has
> completed. Perhaps we can usually assume QtRuby should delete the 'char
> *',
> but special case when it shouldn't - tricky..

I've been pondering this for the past 15 minutes or so now, and I haven't
thought of any *good* solutions.  I'm curious what PerlQt does to handle
this, if anything.