Another pro is that the core code can always use more review. There are bugs, and sometimes they are surprisingly findable.

For instance Ovid also wrote use CGI or die;, which includes among the benefits of CGI.pm that hand-rolled solutions don't tend to test $ENV{CONTENT-LENGTH} to catch aborted downloads. Well it was by reading the source-code that I found that a hard-to-debug problem happened because CGI.pm didn't either on a regular POST. (Only on a multi-part post.)

And even if you don't find any bugs in reviewing a bunch of that code, you will get insight into ways that very smart people who you have never met think. This is never a bad thing (even if the state of the art has progressed).

For a possible, if anyone wants to read Code Reading: The Open Source Perspective and get back on how it is, I would be interesting. I would have read it, but I have been busy learning stuff (eg Oracle) for a new job...


In reply to Re: Reasons for looking at your favourite module's source by tilly
in thread Reasons for looking at your favourite module's source by liz

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.