Command-line parameter specification.
This module replaces , and should be used in all new code. Its types and compositional rules are much easier to understand.
module type S : sig ... end
include S
Command.Param
is intended to be used with the %map_open
syntax defined in
ppx_let
, like so:
let command =
Command.basic ~summary:"..."
[%map_open
let count = anon ("COUNT" %: int)
and port = flag "port" (optional int) ~doc:"N listen on this port"
and person = person_param
in
(* ... command-line validation code, if any, goes here ... *)
fun () ->
(* the body of the command *)
do_stuff count port person
]
One can also use %map_open
to define composite command line parameters, like
person_param
in the previous snippet:
type person = { name : string; age : int }
let person_param : person Command.Param.t =
[%map_open
let name = flag "name" (required string) ~doc:"X name of the person"
and age = flag "age" (required int) ~doc:"N how many years old"
in
{name; age}
]
The right hand sides of %map_open
definitions have Command.Param
in scope.
Alternatively, you can say:
let open Foo.Let_syntax in
[%map_open
let x ...
]
if Foo
follows the same conventions as Command.Param
.
See example/command/main.ml for more examples.
include Core__.Import.Applicative.S with type a t := a t
val return : 'a ‑> 'a t
module Applicative_infix : sig ... end
val flag : ?aliases:string list ‑> ?full_flag_required:unit ‑> string ‑> 'a Flag.t ‑> doc:string ‑> 'a t
flag name spec ~doc
specifies a command that, among other things, takes a flag
named name
on its command line. doc
indicates the meaning of the flag.
All flags must have a dash at the beginning of the name. If name
is not prefixed
by "-", it will be normalized to "-" ^ name
.
Unless full_flag_required
is used, one doesn't have to pass name
exactly on the
command line, but only an unambiguous prefix of name
(i.e., a prefix which is not
a prefix of any other flag's name).
NOTE: the doc
for a flag which takes an argument should be of the form
arg_name ^ " " ^ description
where arg_name
describes the argument and
description
describes the meaning of the flag.
NOTE: flag names (including aliases) containing underscores will be rejected. Use dashes instead.
NOTE: "-" by itself is an invalid flag name and will be rejected.
val flag_optional_with_default_doc : ?aliases:string list ‑> ?full_flag_required:unit ‑> string ‑> 'a Arg_type.t ‑> ('a ‑> Core__.Import.Sexp.t) ‑> default:'a ‑> doc:string ‑> 'a t
flag_optional_with_default_doc name arg_type sexp_of_default ~default ~doc
is a shortcut for flag
, where:
Flag.t
is optional_with_default default arg_type
doc
is passed through with an explanation of what the default value
appended.values included for convenience so you can specify all command line parameters inside
a single local open of Param
module Arg_type : module type of Arg_type with type 'a Arg_type.t = 'a Arg_type.t
include module type of Arg_type.Export
val string : string Arg_type.t
val int : int Arg_type.t
Beware that an anonymous argument of type int
cannot be specified as negative,
as it is ambiguous whether -1 is a negative number or a flag. (The same applies
to float
, time_span
, etc.) You can use the special built-in "-anon" flag to
force a string starting with a hyphen to be interpreted as an anonymous argument
rather than as a flag, or you can just make it a parameter to a flag to avoid the
issue.
val char : char Arg_type.t
val float : float Arg_type.t
val bool : bool Arg_type.t
val date : Core__.Import.Date.t Arg_type.t
val percent : Core__.Import.Percent.t Arg_type.t
val time : Core__.Import_time.Time.t Arg_type.t
val time_zone : Core__.Import_time.Time.Zone.t Arg_type.t
val time_span : Core__.Import_time.Time.Span.t Arg_type.t
val host_and_port : Core__.Import.Host_and_port.t Arg_type.t
val ip_address : Unix.inet_addr Arg_type.t
val sexp : Core__.Import.Sexp.t Arg_type.t
val sexp_conv : (Core__.Import.Sexp.t ‑> 'a) ‑> 'a Arg_type.t
include module type of Flag with type a Flag.t := a Flag.t
Command-line flag specifications
val optional_with_default : 'a ‑> 'a Arg_type.t ‑> 'a t
optional_with_default
flags may be passed at most once, and
default to a given value
val one_or_more : 'a Arg_type.t ‑> ('a * 'a list) t
one_or_more
flags must be passed one or more times
val no_arg : bool t
no_arg
flags may be passed at most once. The boolean returned
is true iff the flag is passed on the command line
val no_arg_register : key:'a Core__.Import.Univ_map.With_default.Key.t ‑> value:'a ‑> bool t
no_arg_register ~key ~value
is like no_arg
, but associates value
with key
in the in the auto-completion environment
val no_arg_abort : exit:(unit ‑> Core__.Import.never_returns) ‑> unit t
no_arg_abort ~exit
is like no_arg
, but aborts command-line parsing
by calling exit
. This flag type is useful for "help"-style flags that
just print something and exit.
val escape : string list option t
escape
flags may be passed at most once. They cause the command line parser to
abort and pass through all remaining command line arguments as the value of the
flag.
A standard choice of flag name to use with escape
is "--"
.
include module type of Anons with type a Anons.t := a Anons.t
Anonymous command-line argument specification.
val (%:) : string ‑> 'a Arg_type.t ‑> 'a t
(name %: typ)
specifies a required anonymous argument of type typ
.
The name
must not be surrounded by whitespace, if it is, an exn will be raised.
If the name
is surrounded by a special character pair (<>, {}, [] or (),)
name
will remain as-is, otherwise, name
will be uppercased.
In the situation where name
is only prefixed or only suffixed by one of the
special character pairs, or different pairs are used, (e.g. "<ARG]") an exn will
be raised.
The (possibly transformed) name
is mentioned in the generated help for the
command.
sequence anons
specifies a sequence of anonymous arguments. An exception
will be raised if anons
matches anything other than a fixed number of
anonymous arguments
non_empty_sequence_as_pair anons
and non_empty_sequence_as_list anons
are like
sequence anons
except that an exception will be raised if there is not at least
one anonymous argument given.
t2
, t3
, and t4
each concatenate multiple anonymous argument
specs into a single one. The purpose of these combinators is to allow
for optional sequences of anonymous arguments. Consider a command with
usage:
main.exe FOO [BAR BAZ]
where the second and third anonymous arguments must either both be there or both not be there. This can be expressed as:
t2 ("FOO" %: foo) (maybe (t2 ("BAR" %: bar) ("BAZ" %: baz)))]
Sequences of 5 or more anonymous arguments can be built up using nested tuples:
maybe (t3 a b (t3 c d e))