Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
Hi all. I have recently uploaded a module to CPAN, Math::Derivative_XS that provides a C/XS optimised version of one of the functions in Math::Derivative (with more to follow).

I'm wondering what people think about the following questions:

  1. Putting XS in a separate module - I think it's a good idea since it leaves the base module Pure Perl.
  2. Naming such a module by adding _XS on the end - seems to be the defacto standard
  3. Having the module inherit from the Pure Perl version vs. being purely standalone - in this case I only implement one function, so requiring the parent module as a dependency is required anyway to defer those functions.
  4. Best practise for testing - my XS module has a test to check for any regressions compared to the Pure Perl base. I would suggest this as a best practise, but in this case the parent module unfortunately has no tests at all. So I guess my question is when I do write some proper tests, should they go into the _XS module that I manage or (more probably) should I put them into the base Pure Perl package (and then by implication the regression tests in the _XS module will in effect be validating those tests).
Any other thoughts also welcome!


In reply to On naming of XS extension modules by aufflick

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!
  • 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, 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, 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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (14)
    As of 2015-07-01 19:25 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









      Results (17 votes), past polls