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

Re: tr funkiness in 5.6.[12] (but not 5.6.0!)

by JavaFan (Canon)
on Jan 07, 2009 at 00:26 UTC ( [id://734525]=note: print w/replies, xml ) Need Help??


in reply to tr funkiness in 5.6.[12] (but not 5.6.0!)

Well, I guess you've found a bug in the last release of a really old version of Perl. 5.6.1 dates from the first half of 2001 - George W. Bush was only president for 2.5 months (5.6.2 just fixed build issues). In seems that the bug has been fixed in the (almost) 8 years that have passed since. You've also found a workaround for the bug.

What else do you want? Noone is going to use the time machine to travel back to 2001 and fix 5.6.1.

  • Comment on Re: tr funkiness in 5.6.[12] (but not 5.6.0!)

Replies are listed 'Best First'.
Re^2: tr funkiness in 5.6.[12] (but not 5.6.0!)
by belg4mit (Prior) on Jan 07, 2009 at 16:21 UTC
    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.

      How about an explanation, as indicated in the original message?
      The answer "it's a bug", as indicated in the first reply isn't good enough? If you want details of what caused the bug, get a git clone of the perl source, and run 'git-bisect' between 5.6.0 and 5.6.1 to see which commit first triggers the unwanted behaviour.
        Not really, no. It's a bit like saying "Because." Following Dominus' pearl of wisdom
        #11943 Ah yes, and you are the first person to have noticed this bug since 1987. Sure.
        I posted the question to see if anyone had any prior knowledge of the matter; after having conducted a search of course.

        Thank you anyways,

        --
        In Bob We Trust, All Others Bring Data.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://734525]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others avoiding work at the Monastery: (5)
As of 2024-04-22 16:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found