Skip to content

Commit d67df10

Browse files
committed
Clarity for commands vs global options
Signed-off-by: Mike Brown <[email protected]>
1 parent 933b55d commit d67df10

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

runtime.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,11 @@ $ funC [global-options] <COMMAND> [command-specific-options] <command-specific-a
99

1010
## Global options
1111

12-
None are required, but the runtime may support options that start with at least one hyphen.
13-
Global options may take positional arguments (e.g. `--log-level debug`), but the option parsing must be such that `funC <COMMAND>` is unambiguously an invocation of `<COMMAND>` for any `<COMMAND>` that does not start with a hyphen (including commands not specified in this document).
12+
None are required, but the runtime MAY support options that start with at least one hyphen.
13+
Global options MAY take positional arguments (e.g. `--log-level debug`).
14+
Command names MUST not start with hyphens.
15+
The option parsing MUST be such that `funC <COMMAND>` is unambiguously an invocation of `<COMMAND>` (even for commands not specified in this document).
16+
If the runtime is invoked with an unrecognized command, it MUST exit with a nonzero exit code and MAY log a warning to stderr.
1417

1518
## Character encodings
1619

0 commit comments

Comments
 (0)