Issue #6648 has been updated by nobu (Nobuyoshi Nakada). Eregon (Benoit Daloze) wrote in #note-31:

mame (Yusuke Endoh) wrote in #note-23:

...

[...] instead of parsing the command line to a string array and passing it to `Kernel#exec`.

Don't we use `execve()` (which takes `char**`) as well on Windows for `Kernel#exec`? It does seem to exist: https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/execve-wex...

`Kernel#exec` is not implemented on Windows.

Did you mean `Kernel#spawn`/`Kernel#system` maybe?

Argument passing is same for them. Eregon (Benoit Daloze) wrote in #note-32:

And from a quick look there is also [`_spawnv`](https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/spawnv-wsp...) which does take a `char**`, maybe we could use that on Windows?

`_spawnv` is not an API but a just wrapper of `CreateProcess` as well as `rb_w32_uspawn`, but lacks some arguments. We use `rb_w32_uspawn` and `rb_w32_uspawn_flags` to support redirection and a few flags. Our functions are designed based on `_spawnv` in msvcrt, so the security concern is similar. The argument handling would work fine for many commands using msvcrt or `ruby`, but not all. mame (Yusuke Endoh) wrote in #note-23:

If you really want to "launch subprocess Ruby instances with the same settings", we might want to consider a more dedicated API for it, instead of parsing the command line to a string array and passing it to `Kernel#exec`.

This means a restricted method to invoke only `ruby` not to run other arbitrary commands, which can interpret the arguments wrongly, by "a more dedicated API", I think. ---------------------------------------- Feature #6648: Provide a standard API for retrieving all command-line flags passed to Ruby https://bugs.ruby-lang.org/issues/6648#change-109127 * Author: headius (Charles Nutter) * Status: Assigned * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- Currently there are no standard mechanisms to get the flags passed to the currently running Ruby implementation. The available mechanisms are not ideal: * Scanning globals and hoping they have not been tweaked to new settings * Using external wrappers to launch Ruby * ??? Inability to get the full set of command-line flags, including flags passed to the VM itself (and probably VM-specific) makes it impossible to launch subprocess Ruby instances with the same settings. A real world example of this is "((%bundle exec%))" when called with a command line that sets various flags, a la ((%jruby -Xsome.vm.setting --1.9 -S bundle exec%)). None of these flags can propagate to the subprocess, so odd behaviors result. The only option is to put the flags into an env var (((|JRUBY_OPTS|)) or ((|RUBYOPT|))) but this breaks the flow of calling a simple command line. JRuby provides mechanisms to get all its command line options, but they require calling Java APIs from Ruby's API set. Rubinius provides its own API for accessing comand-line options, but I do not know if it includes VM-level flags as well as standard Ruby flags. I know there is a (({RubyVM})) namespace in the 2.0 line. If that namespace is intended to be general-purpose for VM-level features, it would be a good host for this API. Something like... ``` class << RubyVM def vm_args; end # returns array of command line args *not* passed to the target script def script; end # returns the script being executed...though this overlaps with $0 def script_args; end # returns args passed to the script...though this overlaps with ARGV, but that is perhaps warranted since ARGV can be modified (i.e. you probably want the original args) end ``` -- https://bugs.ruby-lang.org/