Vladimir Marek <[EMAIL PROTECTED]> writes: >Hello all, > >I do have C++ object typemapped into perl class. Then I have two >functions which creates and destroys that object > >create_object ($obj); >destroy_object ($obj); > >first function is easy, I create the object like: >c_obj *x=new c_obj; >sv_setref_pv( ST(0)), CLASS, (void*)x ); >SvSETMAGIC(ST(0)); > >but the destroy_function has to call delete on the object (sometime, in >another thread, I can't stop that), but I don't know how to >de-mortalize' variable, >in order to stop perl to call destructor on it >again.
Do you mean mortal in the sv_2mortal() sense? Avoiding that is easy - all that a "mortal" SV does is an automatic SvREFCNT_dec() on scope exit. So you can de-mortalize by SvREFCNT_inc(). Tk for example is quite like above - when a widget is created its object has SvREFCNT_inc'ed higher than you might expect and $widget->destroy does corresponding SvREFCNT_dec(s). Then perl calls DESTROY which free()s the memory. But this path risks leaks unless you are very sure that destroys get called. Why are you having destroy_object of your own rather than letting perl track usage and eventually call DESTROY once? >One solution is to create copy of the object and free that copy, >but I would like to do it without copying. sv_setref_pv() puts the pointer in the SvIV slot. So you can de-associate the SV from the C++ thing by zeroing the SvIV. But then destroy_object needs to be prepared to do nothing when passed NULL. > >Thank you > Vladimir Marek
