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

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.