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.
| [reply] |
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.
| [reply] |
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.
| [reply] |
