Ripper is still 2.0 grammar and has not been updated for 2.2 changes #2427
Milestone
Comments
|
I fixed this for rc1 actually but I will mark here so it shows up in some release notes. |
yujinakayama
added a commit
to rspec/rspec-core
that referenced
this issue
Oct 30, 2015
Ripper might fail to parse a Ruby source even if the current runtime parsed it properly, because some versions of JRuby have different implementation of runtime parser and Ripper parser. jruby/jruby#2427 So we handle the syntax error in Ripper and fall back to the simple single line extraction in that case.
yujinakayama
added a commit
to rspec/rspec-core
that referenced
this issue
Oct 30, 2015
Ripper might fail to parse a Ruby source even if the current runtime parsed it properly, because some versions of JRuby have different implementation of runtime parser and Ripper parser. jruby/jruby#2427 So we handle the syntax error in Ripper and fall back to the simple single line extraction in that case.
yujinakayama
added a commit
to rspec/rspec-core
that referenced
this issue
Oct 30, 2015
Ripper might fail to parse a Ruby source even if the current runtime parsed it properly, because some versions of JRuby have different implementation of runtime parser and Ripper parser. jruby/jruby#2427 So we handle the syntax error in Ripper and fall back to the simple single line extraction in that case.
yujinakayama
added a commit
to rspec/rspec-core
that referenced
this issue
Oct 30, 2015
Ripper might fail to parse a Ruby source even if the current runtime parsed it properly, because some versions of JRuby have different implementation of runtime parser and Ripper parser. jruby/jruby#2427 So we handle the syntax error in Ripper and fall back to the simple single line extraction in that case.
myrridin
pushed a commit
to myrridin/rspec-core
that referenced
this issue
Dec 11, 2015
Ripper might fail to parse a Ruby source even if the current runtime parsed it properly, because some versions of JRuby have different implementation of runtime parser and Ripper parser. jruby/jruby#2427 So we handle the syntax error in Ripper and fall back to the simple single line extraction in that case.
MatheusRich
pushed a commit
to MatheusRich/rspec-core
that referenced
this issue
Oct 30, 2020
Ripper might fail to parse a Ruby source even if the current runtime parsed it properly, because some versions of JRuby have different implementation of runtime parser and Ripper parser. jruby/jruby#2427 So we handle the syntax error in Ripper and fall back to the simple single line extraction in that case.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ripper is still 2.0 grammar and has not been updated for 2.2 changes
The text was updated successfully, but these errors were encountered: