From: "nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "nobu (Nobuyoshi Nakada)" <noreply@ruby-lang.org>
Subject: [ruby-core:117103] [Ruby master Feature#20329] Clean up `--dump` sub-options
Date: Tue, 12 Mar 2024 03:22:03 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-107176.20240312032203.4@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20329.20240308094629.4@ruby-lang.org
Issue #20329 has been updated by nobu (Nobuyoshi Nakada).
`--dump=insns` will not be changed.
Since `+` is the separator, `insns+-opt` will be same as the current `insns_without_opt`.
----------------------------------------
Feature #20329: Clean up `--dump` sub-options
https://bugs.ruby-lang.org/issues/20329#change-107176
* Author: nobu (Nobuyoshi Nakada)
* Status: Open
----------------------------------------
Currently we have 5 options for `--dump` command line option.
* insns
* insns_without_opt
* yydebug(+error-tolerant)
* parsetree(+error-tolerant)
* parsetree_with_comment(+error-tolerant)
Among these, `insns_without_opt` is a variant of `insns`, and `parsetree_with_comment` is a variant of `parsetree`.
However, there is now another way to specify variants (e.g. `+error-tolerant`).
How about unifying the two so that the former can also be specified in the same form, such as `--dump=parsetree+comment+error-tolerant`?
It also will be able to abbreviate as parse+comm+err` or more.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next prev parent reply other threads:[~2024-03-12 3:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 9:46 [ruby-core:117088] [Ruby master Feature#20329] Clean up `--dump` sub-options nobu (Nobuyoshi Nakada) via ruby-core
2024-03-11 5:00 ` [ruby-core:117097] " k0kubun (Takashi Kokubun) via ruby-core
2024-03-12 3:22 ` nobu (Nobuyoshi Nakada) via ruby-core [this message]
2024-03-13 10:00 ` [ruby-core:117128] " eightbitraptor (Matthew Valentine-House) via ruby-core
2024-03-18 14:21 ` [ruby-core:117209] " nobu (Nobuyoshi Nakada) via ruby-core
2024-03-18 15:40 ` [ruby-core:117211] " eightbitraptor (Matthew Valentine-House) 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.journal-107176.20240312032203.4@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.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).