Terminate argument parsing on --
#10726
Conversation
encountering a -- terminates getopt option parsing and the rest of the options are part of ARGS closes #10226
|
👍 |
|
[image: 👍] |
Terminate argument parsing on `--`
| println(STDERR, "julia: option `$arg` is missing an argument") | ||
| exit(1) | ||
| end | ||
| idxs = find(x -> x == "--", args) |
There was a problem hiding this comment.
what's the rationale for blocking the -- symbol from user arguments? the usual use of the -- flag is to permit use of -- as a filename (or other filenames that look like flags) to be permitted as an unprocessed inputs. as such, it seems odd to me to unconditionally block them.
i would also have expected the following to be valid to allow chaining, where -- terminates argument parsing for each subsequent parsing of ARGS:
./julia -f -- ./filename.jl -- first args -- user argscurrently, however, it doesn't get anywhere:
$ ./julia -f -- ./filename.jl -- first args -- user args
julia: redundant option terminator `--`
There was a problem hiding this comment.
No reason. @vtjnash can you point to a source that explains this in more detail or gives an example? I've never seen what you have pointed out in the wild.
There was a problem hiding this comment.
gives an example
Do you mean to use -- to allow option like file name? Or allowing nesting it.
For the first one, I think most coreutils have that.
For the second one, at least the ArchLinux dev-tools is using it to allow passing arguments to different components in the chroot toolchain.
encountering a -- terminates getopt option parsing
and the rest of the options are part of ARGS
closes #10226