From: "tompng (tomoya ishida)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:109798] [Ruby master Bug#18988] # Ripper cannot parse some code that has regexp named capture
Date: Wed, 31 Aug 2022 16:05:52 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-18988.20220831160551.10330@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-18988.20220831160551.10330@ruby-lang.org
Issue #18988 has been reported by tompng (tomoya ishida).
----------------------------------------
Bug #18988: # Ripper cannot parse some code that has regexp named capture
https://bugs.ruby-lang.org/issues/18988
* Author: tompng (tomoya ishida)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.2.0dev (2022-08-29T15:47:09Z :detached: cd7506593a) [x86_64-linux]
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
Ripper does not seems to recognize regexp named capture defining new local variables, fails to parse some code.
~~~ruby
requie 'ripper'
# expect syntax ok, got syntax error
Ripper.sexp("/(?<a>)/ =~ ''; x = a **a, a if false")
# expect syntax error, got syntax ok
Ripper.sexp("/(?<a>)/ =~ ''; x = a **a, **a if false")
# "exit" is a method call, got string_literal
Ripper.sexp("/(?<a>)/ =~ ''; a %(exit)")
~~~
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2022-08-31 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 16:05 tompng (tomoya ishida) [this message]
2023-08-31 3:21 ` [ruby-core:114601] [Ruby master Bug#18988] Ripper cannot parse some code that has regexp named capture jeremyevans0 (Jeremy Evans) via ruby-core
2024-02-20 12:00 ` [ruby-core:116878] " yui-knk (Kaneko Yuichiro) via ruby-core
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-18988.20220831160551.10330@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).