From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:71726] [Ruby trunk - Bug #11748] [Closed] [BACKPORT] ripper misses on_tstring_content callback result
Date: Sun, 29 Nov 2015 00:06:13 +0000 [thread overview]
Message-ID: <redmine.issue-11748.20151129000612.5028a5962d9c09e9@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11748.20151129000612@ruby-lang.org
Issue #11748 has been reported by Nobuyoshi Nakada.
----------------------------------------
Bug #11748: [BACKPORT] ripper misses on_tstring_content callback result
https://bugs.ruby-lang.org/issues/11748
* Author: Nobuyoshi Nakada
* Status: Closed
* Priority: Normal
* Assignee:
* ruby -v:
* Backport: 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: REQUIRED
----------------------------------------
2.2以降、on_tstring_contentコールバックの戻り値が捨てられています。
~~~
$ ruby2.0 -rripper -e 'p Ripper.sexp("<<E\nx\nE")'
[:program, [[:string_literal, [:string_content, [:@tstring_content, "x\n", [2, 0]]]]]]
$ ruby2.1 -rripper -e 'p Ripper.sexp("<<E\nx\nE")'
[:program, [[:string_literal, [:string_content, [:@tstring_content, "x\n", [2, 0]]]]]]
$ ruby2.2 -rripper -e 'p Ripper.sexp("<<E\nx\nE")'
[:program, [[:string_literal, [:string_content, "x\n"]]]]
~~~
r52777のバックポートをお願いします。
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2015-11-28 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11748.20151129000612@ruby-lang.org>
2015-11-29 0:06 ` nobu [this message]
2015-12-01 18:16 ` [ruby-core:71782] [Ruby trunk - Bug #11748] [BACKPORT] ripper misses on_tstring_content callback result nagachika00
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-11748.20151129000612.5028a5962d9c09e9@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).