Florian Frank wrote:
> Andrew Walrond wrote:
>
>> This is a long standing bug in Ruby, and has been
>> reported hundreds of times by myself and many other
>> people, but never addressed. Unfortunately, the usual
>> response is "Give a small code example reproducing the
>> problem", which is impossible (given the nature of the
>> bug), so it gets overlooked.
>>
>>
> No, the message alone doesn't say very much, because it's
> printed if a default case of the evluator is reached. So
> it's perfectly possible that every report of the hundred
> was caused by a different bug. That's why you and
> everyone that encounters it should provide a code
> example. And BTW, whining still isn't a substitute for
> that...

But the code sample is worthless.  What fails on my machine works on someone
else's machine. I posted a post like this a couple weeks ago and the
response I got was: "works on my machine".  And the mere act of inserting a
newline or removing a newline can break or fix the problem.