I'm sure that I occupy a substantially lower station than Ovid does in this community, because I feel that I will have a tendency to post more questions than answers in the near future. To that end, I would point out that I crafted the code that I submitted in Why is this link parser only working the first time? as carefully as I could. I did so because I did not want to embarass myself, nor waste the other members' time. As you can see if you follow the thread, I was rewarded with two helpful answers.

tilly's response, which concisely answered my question, did not need to be written in a clean programming style. In fact, I suggest that a more lengthy, more stylistic response would have been harder for a subsequent Seeker of Wisdom to follow. And the result was that I felt a responsibility to summarize the situation after I followed the advice provided.

Perhaps it is more important, from a community learning perspective, that at least one side of the code-related question be written in good form.

Dave Aiello
Chatham Township Data Corporation

In reply to Re: (Ovid -- Programming style - Off topic) Re: Silly code reviews and shift by dave_aiello
in thread Silly code reviews and shift by tilly

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.