diff options
| author | Alex Flint <[email protected]> | 2015-11-03 08:15:45 -0800 |
|---|---|---|
| committer | Alex Flint <[email protected]> | 2015-11-03 08:15:45 -0800 |
| commit | 518564234843a9512210eb34d8900bb5d12b7c4c (patch) | |
| tree | cae8a2ea25c9f822f6be6d4b458f3db066e555d2 | |
| parent | 95bf6f25e0095ba2166439eb4e47aa08ddd5c49b (diff) | |
fix note on boolean flags in readme
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -121,7 +121,7 @@ https://godoc.org/github.com/alexflint/go-arg There are many command line argument parsing libraries for Go, including one in the standard library, so why build another? -The shortcomings of the `flag` library that ships in the standard library are well known. Positional arguments must preceed options, so `./prog x --foo=1` does what you expect but `./prog --foo=1 x` does not. Boolean arguments must have explicit values, so `./prog -debug=1` sets debug to true but `./myprog -debug` does not. +The shortcomings of the `flag` library that ships in the standard library are well known. Positional arguments must preceed options, so `./prog x --foo=1` does what you expect but `./prog --foo=1 x` does not. Arguments cannot have both long (`--foo`) and short (`-f`) forms. Many third-party argument parsing libraries are geared for writing sophisticated command line interfaces. The excellent `codegangsta/cli` is perfect for working with multiple sub-commands and nested flags, but is probably overkill for a simple script with a handful of flags. |
