|
|
|
|
|
|
by arp242
450 days ago
|
|
|
> it's consistent in the Go community. Except it's not? There are tons of flag packages in real use, because the stdlib one kind of sucks. Even the "go" tool itself works around some of its limitations (things like "go test ./... -v" won't work out of the box, since it will stop parsing flags at the first non-flag, so the go command reorders os.Args before sending it off to the flag package). Things like "-a 1 2 3" are not standard "Go style" at all. I've never seen that. |
|
|
It doesn’t. It’s simpler, which makes it not suck in my books.
All the stuff about short vs long, grouping short flags together, allowing the last flag of a group of short flags to take an argument, allowing a flag to take multiple values, etc. is cool, but confusing and quite hard to do right.
In Go it’s just -flag[=value].