You can see this implementation on our repo.

I'm not going to review your code.

newSV_type is a new addition to the core. If you want to support older Perls, you'll have to use something else, or include ppport (which isn't hard, and will handle other such problems if any). I chose newSV_type because it doesn't create a string buffer that will end up being freed.

What are the fragile issues that you can see?

I was referring to how easy it is to accidentally replace the PV. If it's a private interface between your XS and Perl components, no problem. If it's a public interface, it's a problem.

What more can I do ensure memory handling is done correctly

Test your code using valgrind.

In reply to Re^3: Writing to Pointer Values (PV) in XS by ikegami
in thread Writing to Pointer Values (PV) in XS by kthakore

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.