Since the following is a valid self-contained script: ~~~ ruby p DATA.read # comment __END__ abc ~~~ should the `__END__` suffix data be preserved with `:on___end__` ? Alternatively should there be an `:on_ignored___end` toke...mjago (Martyn Jago)
I'm very sorry nobu, I copy and pasted the wrong script. This is what I meant to express: ~~~ diff -u <(ruby -v -rripper -rpp -e 'pp Ripper.lex("<<-E\n\#{1} \#{2}\nE")') \ <(ruby -v -rripper -rpp -e 'pp Ripper.lex("<<~E\n\#{1} \#...mjago (Martyn Jago)
Where you have two or more embedded expressions on the same line within a squiggly heredoc seperated by whitespace, Ripper considers that whitespace as ignored space despite it not being at the beginning of a line. Below is a diff of l...mjago (Martyn Jago)
The Ruby formatter rufo has exposed a ripper parsing error when parsing the following ruby code: ~~~ ruby proc { |(w, *x, y), z| } ~~~ The s-expression below shows that the *y identifier* is swallowed. The following ruby spec ...mjago (Martyn Jago)
mjago (Martyn Jago)08:15 AM Ruby Bug #14046 (Closed): Ripper loses DATA