Front page | perl.perl5.porters |
Postings from January 2016
I am not respond to any particular post in this ticket.
There are 4 ways to store C resources (pointers or self-alloced-C structs) in Perl.
Pointers only, in a SVIV
Pointers and C structs, in a SVPV that is 4, 8 or more (self alloced C structs) bytes long, but filled with binary gibberish ("packed pointers")
Pointers and C structs, in a MG struct, completely unreachable from PP, cons, must search the linked list of magic each time in an XSUB
#4 is rare, inside out objects with the pointer or C struct stored with one of the above methods in a global perl var, serializing the object is impossible with inside out objects because they are indexed by HV*s which change between perl process runs
There is a number 5 way but such an object is insane.
Pointers only, in the XSANY of a XSUB CV *, your object is reference to a blessed (X) subroutine, dtor is free magic attached to the CV *. I dont think Storable can deparse an XSUB and recreate it.
--
bulk88 ~ bulk88 at hotmail.com
---
via perlbug: queue: perl5 status: rejected
https://rt.perl.org/Ticket/Display.html?id=127232
Thread Previous