Greetings, fellow monks

After a recent discussion (it was not heated enough to be a full blown flamethrower free-for-all) with some of my comrades on the topic of performance versus (ease of use|development time) I began to wonder about the way one could write part of (or all) a perl module in C.

The reason behind it is the following : after some work on that C assignment of mine I became aware that I completely overlooked some development aspects in my prototype : the profiling.
Then, as I grudgingly tread on that path on the final version of the project I started daydreaming a bit about how such a project would make more sense written in Perl (I already thought that when I wrote the Perl prototype). Then the discussion I started by talking about came back to my mind and I thought that it would be very nice to be able to rewrite in C/asm the parts singled out by the profiler.

So, on I went, collecting pdf printouts of perlxs, perlxstut, h2xs, perlguts and perlapi. As I read through the material I wonder, has anyone here done it and would be willing to share about h(is|er) experience? Were the rewards (at list the quantifiable ones) enough to justify the hassle of going low level? Thank you for your input


In reply to Perl Module written in C/asm by QuillMeantTen

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.