The beauty of mirroring the C++ api is you're mirroring the C++ api -- its like the same API, same names, same usage (basically)

Well, fair enough. This way of "recycling" the FastqRecord object seems awkward in an otherwise OO module (at least to someone who learned Perl first and only later delved into C/C++). I do see your point, however - sticking as close as possible to the C++ API probably has the least potential for confusion and will be easiest to maintain.

Avoid XS as much as possible, unless you want to learn a lot about XS instead of just getting on with whatever task you have to complete

That is advice that I have no problem embracing.

In reply to Re^2: "Perlifying" an XSpp method by jdv
in thread "Perlifying" an XSpp method by jdv

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.