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

I haven't seen this bug in a while, but it was a very strange one for
me...

1. It happened sometimes when I was not (to my knowledge) using *any*
C extension.

2. Frequently ANY change in the source would make it go away -- e.g.,
adding a blank line or a comment.


Hal