Chapter 6. Zend_Console_Getopt
Prev     Next

Chapter 6. Zend_Console_Getopt

Table of Contents

6.1. Introduction to Getopt
6.2. Declaring Getopt Rules
6.2.1. Declaring Options with the Short Syntax
6.2.2. Declaring Options with the Long Syntax
6.3. Fetching Options and Arguments
6.3.1. Handling Getopt Exceptions
6.3.2. Fetching Options by Name
6.3.3. Reporting Options
6.3.4. Fetching Non-option Arguments
6.4. Configuring Zend_Console_Getopt
6.4.1. Adding Option Rules
6.4.2. Adding Help Messages
6.4.3. Adding Option Aliases
6.4.4. Adding Argument Lists
6.4.5. Adding Configuration

6.1. Introduction to Getopt

The Zend_Console_Getopt class helps command-line applications to parse their options and arguments.

Users may specify command-line arguments when they execute your application. These arguments have meaning to the application, to change the behavior in some way, or choose resources, or specify parameters. Many options have developed customary meaning, for example "--verbose" enables extra output from many applications. Other options may have a meaning that is different for each application. For example, "-c" enables different features in grep, ls, and tar.

Below are a few definitions of terms. Common usage of the terms varies, but this documentation will use the definitions below.

  • "argument": a string that occurs on the command-line following the name of the command. Arguments may be options or else may appear without an option, to name resources on which the command operates.

  • "option": an argument that signifies that the command should change its default behavior in some way.

  • "flag": the first part of an option, identifies the purpose of the option. A flag is preceded conventionally by one or two dashes ("-" or "--"). A single dash precedes a single-character flag or a cluster of single-character flags. A double-dash precedes a multi-character flag. Long flags cannot be clustered.

  • "parameter": the secondary part of an option; a data value that may accompany a flag, if it is applicable to the given option. For example, many commands accept a "--verbose" option, but typically this option has no parameter. However, an option like "--user" almost always requires a following parameter.

    A parameter may be given as a separate argument following a flag argument, or as part of the same argument string, separated from the flag by an equals symbol ("="). The latter form is supported only by long flags. For example, -u username, --user username, and --user=username are forms supported by Zend_Console_Getopt.

  • "cluster": multiple single-character flags combined in a single string argument and preceded by a single dash. For example, "ls -1str" uses a cluster of four short flags. This command is equivalent to "ls -1 -s -t -r". Only single-character flags can be clustered. You cannot make a cluster of long flags.

For example, in "mysql --user=root mydatabase", "mysql" is a command, "--user=root" is an option, "--user" is a flag, "root" is a parameter to the option, and "mydatabase" is an argument but not an option by our definition.

Zend_Console_Getopt provides an interface to declare which flags are valid for your application, output an error and usage message if they use an invalid flag, and report to your application code which flags the user specified.

[Note] Getopt is not an application framework

Zend_Console_Getopt does not interpret the meaning of flags and parameters, nor does this class implement application workflow or invoke application code. You must implement those actions in your own application code. You can use the Zend_Console_Getopt class to parse the command-line and provide object-oriented methods for querying which options were given by a user, but code to use this information to invoke parts of your application should be in another PHP class.

The following sections describe usage of Zend_Console_Getopt.

Prev     Next
5.4. Zend_Config_Xml  Home  6.2. Declaring Getopt Rules