Re^2: Perl, C and deallocation responsibility

Thank you. I hadn't thought of doing that. I think I was stuck on the whole 'must be a PV' thing.

I'll try to play with that when I can!

Comment on Re^2: Perl, C and deallocation responsibility

Replies are listed 'Best First'.
Re^3: Perl, C and deallocation responsibility by etj (Priest) on May 02, 2023 at 13:38 UTC
I would say what's most relevant in your decision is how Perl-dependent you want your C code to be: If you're comfortable with it being Perl-dependent, you would probably want to have all memory allocation/management done by Perl, using probably-mortal SVs, and PVs from the start. If you want to maintain the C code as purely C, then you can use the `typemap` stuff in the various notes here to copy the C-created data into Perl-land, and then `free` the C-allocated memory.	[reply] [d/l] [select]
Re^4: Perl, C and deallocation responsibility by SheWolf (Novice) on May 03, 2023 at 00:38 UTC
Unfortunately I need to make this work in both worlds. I still need to keep the compiled C running, and I need to have it called by Perl. I never choose the easy path!	[reply]