Backport #6200

Ripper uses wrong encoding for heredoc strings

Added by Loren Segal about 3 years ago. Updated about 3 years ago.

[ruby-core:43670]
Status:Closed
Priority:Normal
Assignee:-

Description

The following gist illustrates the issue: https://gist.github.com/2200383

Note that I just tried this in ruby-2.0.0dev (head) and it seems to work fine, but it fails in 1.9.3p125

Can this 2.0 fix to heredoc string encoding be backported?

Associated revisions

Revision 35128
Added by Nobuyoshi Nakada about 3 years ago

merge revision(s) 33542,33543: [Backport #6200]

* parse.y (parser_nextc): set encoding for the buffer of ripper.

History

#1 Updated by Nobuyoshi Nakada about 3 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r35128.
Loren, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


merge revision(s) 33542,33543: [Backport #6200]

* parse.y (parser_nextc): set encoding for the buffer of ripper.

Also available in: Atom PDF