Wednesday 17 January 2018 photo 46/69
|
Posix guidelines: >> http://pqj.cloudz.pw/download?file=posix+guidelines << (Download)
Posix guidelines: >> http://pqj.cloudz.pw/read?file=posix+guidelines << (Read Online)
unix command line options standard
gnu long options
command line argument standards
gnu argument parsing
opengroup posix
posix command line conventions
posix shell
posix commands
On POSIX systems (e.g. Linux, MacOSX), at least for programs possibly started in a shell terminal (e.g. most of them), I would recommend using the GNU coding conventions (which also lists common argument names) and look into the POSIX utilities guidelines, even for proprietary software: always handle
Command-Line Arguments warns that the use of command-line arguments in a Java program may cause that program to be unportable (that is, it will not be 100% Pure Java). If a program requires command-line arguments, then it should follow the POSIX conventions for them. The POSIX conventions are summarized here:.
The getopt() function in the System Interfaces volume of POSIX.1-2008 assists utilities in handling options and operands that conform to these guidelines. Operands and option-arguments can contain characters not specified in the portable character set.
4.7 Standards for Command Line Interfaces. It is a good idea to follow the POSIX guidelines for the command-line options of a program. The easiest way to do this is to use getopt to parse them.
Various bash constructs can't be used in POSIX-conforming shell scripts. If a construct isn't described in the POSIX shell standard, it isn't allowed in POSIX shell scripts. Below is a list of bash-specific constructs that have been sources of trouble in the past: Tests using the
27 Aug 2014 omd - extensible Markdown library and tool in "pure OCaml"
The Portable Operating System Interface (POSIX) is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines the application programming interface (API), along with command line shells and utility interfaces, for software compatibility with variants
25.1.1 Program Argument Syntax Conventions. POSIX recommends these conventions for command line arguments. getopt (see Getopt) and argp_parse (see Argp) make it easy to implement them. Arguments are options if they begin with a hyphen delimiter (' - '). Multiple options may follow a hyphen delimiter in a single
In fact, it seems that POSIX guidelines suggest avoiding options that aren't a single character (though it's not prohibited, just a guideline):. Guideline 3: Each option name should be a single alphanumeric character (the alnum character classification) from the portable character set. The -W (capital-W) option
Annons