Package Usage: go: github.com/ogier/pflag
pflag is a drop-in replacement for Go's flag package, implementing
POSIX/GNU-style --flags.
pflag is compatible with the GNU extensions to the POSIX recommendations
for command-line options. See
http://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
Usage:
pflag is a drop-in replacement of Go's native flag package. If you import
pflag under the name "flag" then all code should continue to function
with no changes.
There is one exception to this: if you directly instantiate the Flag struct
there is one more field "Shorthand" that you will need to set.
Most code never instantiates this struct directly, and instead uses
functions such as String(), BoolVar(), and Var(), and is therefore
unaffected.
Define flags using flag.String(), Bool(), Int(), etc.
This declares an integer flag, -flagname, stored in the pointer ip, with type *int.
If you like, you can bind the flag to a variable using the Var() functions.
Or you can create custom flags that satisfy the Value interface (with
pointer receivers) and couple them to flag parsing by
For such flags, the default value is just the initial value of the variable.
After all flags are defined, call
to parse the command line into the defined flags.
Flags may then be used directly. If you're using the flags themselves,
they are all pointers; if you bind to variables, they're values.
After parsing, the arguments after the flag are available as the
slice flag.Args() or individually as flag.Arg(i).
The arguments are indexed from 0 through flag.NArg()-1.
The pflag package also defines some new functions that are not in flag,
that give one-letter shorthands for flags. You can use these by appending
'P' to the name of any function that defines a flag.
Shorthand letters can be used with single dashes on the command line.
Boolean shorthand flags can be combined with other shorthand flags.
Command line flag syntax:
Unlike the flag package, a single dash before an option means something
different than a double dash. Single dashes signify a series of shorthand
letters for flags. All but the last shorthand letter must be boolean flags.
Flag parsing stops after the terminator "--". Unlike the flag package,
flags can be interspersed with arguments anywhere on the command line
before this terminator.
Integer flags accept 1234, 0664, 0x1234 and may be negative.
Boolean flags (in their long form) accept 1, 0, t, f, true, false,
TRUE, FALSE, True, False.
Duration flags accept any input valid for time.ParseDuration.
The default set of command-line flags is controlled by
top-level functions. The FlagSet type allows one to define
independent sets of flags, such as to implement subcommands
in a command-line interface. The methods of FlagSet are
analogous to the top-level functions for the command-line
flag set.
1 version
Latest release: over 10 years ago
243 dependent packages
View more package details: https://packages.ecosystem.code.gouv.fr/registries/proxy.golang.org/packages/github.com/ogier/pflag
Dependent Repos 7
COSAE-FR/ripacb
RIP ACB Server and clientSize: 91.8 KB - Last synced: 17 days ago - Pushed: 7 months ago

COSAE-FR/ripflow
Simple Netflow v5 probeSize: 25.4 KB - Last synced: 17 days ago - Pushed: almost 4 years ago

COSAE-FR/ripradius
Radius authentication cacheSize: 111 KB - Last synced: 17 days ago - Pushed: 7 months ago

COSAE-FR/riprovision
Provision Unifi devices to specific management VLANsSize: 4.9 MB - Last synced: 17 days ago - Pushed: 2 months ago


COSAE-FR/ripugw
Fake Unifi GatewaySize: 68.4 KB - Last synced: 17 days ago - Pushed: about 2 years ago

COSAE-FR/riputils
Common utilities for RIP projectsSize: 105 KB - Last synced: 17 days ago - Pushed: over 1 year ago
