Quick and dirty patch: https://github.com/ruby/ruby/compare/master...zenspider:ruby:zenspider__encodings?expand=1 This is rough. I'm faking an eval early in the option handling. There is probably a better C way to do this. It is proba...zenspider (Ryan Davis)
Eregon (Benoit Daloze) wrote in #note-2: > I think a better fix, related to this issue, would be to stop checking the class of rescue clauses, I think any expression should be allowed and just call `===` on them. > ... so what should `...zenspider (Ryan Davis)
The actual place where this showed up is in `assert_raises(*exp)` (edited for succinctness): ```ruby def assert_raises *exp msg = "#{exp.pop}.\n" if String === exp.last exp << StandardError if exp.empty? be...zenspider (Ryan Davis)
this works fine (but I don't think it should): ```ruby begin raise "nope" rescue RuntimeError, /why am I allowed?/, "or me?" => e # yay end ``` whereas this version shows a type error, which seems right: ```ruby begin be...zenspider (Ryan Davis)
Closing... I suspect this report is bogus. There doesn't seem to be any registration problems and @byroot pointed out that the C stack looks bogus.zenspider (Ryan Davis)
zenspider (Ryan Davis)08:07 PM Ruby Bug #22425: shield frozen tests in test_rubyoptions.rb from externally defined RUBYOPT