Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
As much as it goes against my grain to feed trolls (why else go on about tangents?)... "What else do you want?" How about an explanation, as indicated in the original message?
doesn't really explain why things have gone awry.
The "work-around" is in name only. The code is the result of parsing user input, and there may be any number of ways of triggering this behavior... again, as indicated in the original message. Some people want band-aids or magic pills, others want to know what caused the accident.

If I'd expected the perl 5.6 tree to be fixed (unlikely without concrete knowledge of what the issue is), I'd have filed a perlbug, and linked it. Instead, I was simply hoping for some inisight and, umm, *wisdom*.

In Bob We Trust, All Others Bring Data.

In reply to Re^2: tr funkiness in 5.6.[12] (but not 5.6.0!) by belg4mit
in thread tr funkiness in 5.6.[12] (but not 5.6.0!) by belg4mit

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.