Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
The traditional Unix utility uses options and arguments to parse command line parms that dictate how the utility should work. Long options is one way to make a utility's usage somewhat natural; for example: util --version. Some utilities use keywords and command/sub-command syntax. It is possible to combine the two without causing too much confusion.
Most system oriented scripters and programmers tend to rely upon the classic Unix model of options and/or arguments; conversely, many programs and scripts use a subcommand structure that is similar to language processing (or lexical checks). Consider that APIs generally use a lexical style interface - in a sense the natrual language idea makes sense if the script or program is going to be called by another program.
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
