Re: Calling call_atexit() to clean up stuff initialized in BOOT

Nicholas Clark wrote:

>>> I understand initialization of an XS module may be modified using  
>>> BOOT.
>>> However, there seems to be no counterpart of BOOT. How do I e.g. free
>>> memory I allocated in BOOT?
[...]
>>> Or is the current practice to write an XS function that e.g. frees the
>>> memory allocate at BOOT and call it in an END handler in the module's
>>> Perl code?
[perl objects]

> Yes, but perl objects are going to be cleaned up (or at least, any with
> DESTROY methods are going to get it called) before then, so that's somewhat
> a red herring.
> 
> But possibly also a solution - anything allocated in BOOT that is stashed
> inside an object will get that object's destroy method called soon after
> END time, with a live interpreter.

I don't create any object in my XS module, it has a pure functional
interface. Is there anything like a destroy function instead of a
destroy method?

-- 
Dipl.-Inform. Gregor Goldbach (PKI Team)
Phone: +49 40 808077-621 Fax: +49 40 808077-556 Mail:[email protected]

DFN-CERT Services GmbH, https://www.dfn-cert.de, Phone  +49 40 808077-555
Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.:  DE 232129737
Sachsenstraße 5,  20097 Hamburg/Germany, CEO: Dr. Klaus-Peter Kossakowski

                       16. DFN-Workshop Sicherheit in vernetzten Systemen
                                          https://www.dfn-cert.de/ws2009/