Fix handling of double dashes -- in crystal eval command#15477
Merged
straight-shoota merged 5 commits intocrystal-lang:masterfrom Feb 22, 2025
Merged
Fix handling of double dashes -- in crystal eval command#15477straight-shoota merged 5 commits intocrystal-lang:masterfrom
-- in crystal eval command#15477straight-shoota merged 5 commits intocrystal-lang:masterfrom
Conversation
straight-shoota
approved these changes
Feb 14, 2025
Co-authored-by: Johannes Müller <straightshoota@gmail.com>
Co-authored-by: Johannes Müller <straightshoota@gmail.com>
Member
|
Ah now the code fails because |
Contributor
Author
|
I tried the following code, but it did not work. It is nighttime in Japan. Good night. # Implementation of the `crystal eval` command
class Crystal::Command
private def eval
compiler = new_compiler
program_source = ""
opt_program_source = nil
program_args = [] of String
parse_with_crystal_opts do |opts|
opts.banner = "Usage: crystal eval [options] [source]\n\nOptions:"
setup_simple_compiler_options compiler, opts
opts.unknown_args do |before_dash, after_dash|
opt_program_source = before_dash.join " "
program_args = after_dash
end
end
if opt_program_source.nil?
program_source = STDIN.gets_to_end
else
program_source = opt_program_source
end
sources = [Compiler::Source.new("eval", program_source)]
output_filename = Crystal.temp_executable "eval"
compiler.compile sources, output_filename
execute output_filename, program_args, compiler
end
end |
Member
|
I pushed a commit with the change I had in mind. |
ysbaddaden
approved these changes
Feb 20, 2025
kojix2
added a commit
to kojix2/crystal
that referenced
this pull request
Feb 23, 2025
…-lang#15477) This allow to pass arguments after a double dash to the program when using the `eval` command. ```console $ crystal eval 'puts ARGV' -- meow neigh ["meow", "neigh"] ``` Previously this caused a parser error (`Error: unexpected token: "meow"`) because the arguments after `--` were still considered code fragments. This could be worked around by two double dashes, but it should really work with just a single one. The reason for this behavior was that the `OptionParser` stops at `--` by default, and removes `--`. We need to use `unknown_args` to distinguish between arguments that were before `--` and arguments that were after `--`. Co-authored-by: Johannes Müller <straightshoota@gmail.com> Fixes: https://forum.crystal-lang.org/t/how-to-use-the-double-hyphen-in-the-eval-subcommand-of-crystal/7742
1 task
Member
|
This change caused a regression, see #15654 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the main part of the pull request #15474
The purpose of this pull request is to pass arguments after a double dash to the program when using the
evalcommand.Expected behavior
Actual behavior
Workaround
By using two double dashes, you can pass arguments to the program as expected.
The reason for this behavior is that the
OptionParserstops at--by default, and removes--.You need to use
unknown_argsto distinguish between arguments that were before--and arguments that were after--.This issue was reported to the forum.