Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Since I didn't know that the problem was not with PAUSE until the node mentioning the patch, I'm not sure that the title wasn't accurate at that point in time. Vague perhaps, but still accurate. A quibble and your point is taken.

I probably should have phrased that better, thanks :)

With the information contained in your question, and the guidance of How do I compose an effective node title?, effective titles might be:

  • FAIL Chess-PGN-EPD-0.25 v5.12.3 MirOS BSD
  • tester fail cpansmoke/perl-5.12.3/cpan/build/Chess-PGN-EPD-0.25
  • Chess-PGN-EPD-0.25/t/01_epdcode.t Non-zero exit status
  • Chess-PGN-EPD-0.25/t/01_epdcode.t Parse errors: Bad plan
  • Chess-PGN-EPD-0.25 Failed 7/8 test programs
  • problem testing Chess-PGN-EPD-0.25
  • Chess-PGN-EPD-0.25 subtest not run on MirOS BSD
"PAUSE problem" makes me think there is a bug PAUSE

In reply to Re^3: PAUSE problem by Anonymous Monk
in thread PAUSE problem by hsmyers

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.