[PHP 4 >= 4.3.0, PHP 5, PHP 7, PHP 8]
getopt — Gets options from the command line argument list
Description
getopt[string $short_options
, array $long_options
= [], int &$rest_index
= null
]: array|false
Parameters
short_options
Each character in this string will be used as option characters and matched against options passed to the script starting with a single hyphen [-
]. For example, an option string "x"
recognizes an option -x
. Only a-z, A-Z and 0-9 are allowed. long_options
An array of options. Each element in this array will be used as option strings and matched against options passed to the script starting with two
hyphens [--
]. For example, an longopts element "opt"
recognizes an option --opt
. rest_index
If the rest_index
parameter is present, then the index where argument parsing stopped will be written to this variable. The short_options
parameter may contain the following elements:
- Individual characters [do not accept values]
- Characters followed by a colon [parameter requires value]
- Characters followed by two colons [optional value]
Option values are the first argument after the string. If a value is required, it does not matter whether the value has leading white space or not. See note.
Note: Optional values do not accept
" "
[space] as a separator.
The long_options
array values may contain:
- String [parameter does not accept any value]
- String followed by a colon [parameter requires value]
- String followed by two colons [optional value]
Note:
The format for the
short_options
andlong_options
is almost the same, the only difference is thatlong_options
takes an array of options [where each element is the option] whereasshort_options
takes a string [where each character is the option].
Return Values
This function will return an array of option / argument pairs, or false
on failure.
Note:
The parsing of options will end at the first non-option found, anything that follows is discarded.
Changelog
7.1.0 | Added the rest_index parameter.
|
Examples
Example #1 getopt[] example: The basics
shell> php example.php -fvalue -h
The above example will output:
array[2] { ["f"]=> string[5] "value" ["h"]=> bool[false] }
Example #2 getopt[] example: Introducing long options
shell> php example.php -f "value for f" -v -a --required value --optional="optional value" --option
The above example will output:
array[6] { ["f"]=> string[11] "value for f" ["v"]=> bool[false] ["a"]=> bool[false] ["required"]=> string[5] "value" ["optional"]=> string[14] "optional value" ["option"]=> bool[false] }
Example #3 getopt[] example: Passing multiple options as one
shell> php example.php -aaac
The above example will output:
array[2] { ["a"]=> array[3] { [0]=> bool[false] [1]=> bool[false] [2]=> bool[false] } ["c"]=> bool[false] }
Example #4 getopt[] example: Using rest_index
$ opt.php -f a b c
Array
[
[f] => a
]
$ opt.php -f 'a b c'
Array
[
[f] => a b c
]
$ opt.php -f "a b c"
Array
[
[f] => a b c
]
$ opt.php -f a\ b\ c
Array
[
[f] => a b c
]
$
ch2902 ¶
9 years ago
Sometimes you will want to run a script from both the command line and as a web page, for example to debug with better output or a command line version that writes an image to the system but a web version that prints the image in the browser. You can use this function to get the same options whether passed as command line arguments or as $_REQUEST values.
Example
Matt ¶
4 years ago
Beware, this function can be dangerous for options following arguments when, for example, you make use of a --dry-run option, due to this behaviour:
"Note: The parsing of options will end at the first non-option found, anything that follows is discarded."
My script was doing a live run even though I specified --dry-run as the last part of the command like this `php foo.php arg1 --dry-run`: getopt[] did NOT include dry-run in its list of options resulting in my script executing a live run.
Anonymous ¶
11 years ago
getopt[] only returns the options specified if they were listed in the options.
So you cant make a switch[] use default: to complain of an unknown option. :[
housni dot yakoob at NOSPAM dot gmail dot com ¶
7 years ago
To elaborate on what 'ch2902' said, there certainly are instances where you may need to execute a script via CLI and the HTTP protocol. In such an instance, you can normalize how your script parses via CLI [using getopt[]] as well as via HTTP [using $_GET] with the following simplified code:
The above code would yield the results below when access via CLI and HTTP.
/**
* params = foo/bar
* username = housni.yakoob
*/
// CLI
$ php script.php --params=foo/bar --username=housni.yakoob
Array
[
[params] => foo/bar
[username] => housni.yakoob
[os] =>
[env] =>
]
// HTTP
script.php?params=foo/bar&username=housni.yakoob
Array
[
[params] => foo/bar
[username] => housni.yakoob
[os] =>
[env] =>
]
/**
* params = foo/bar
* username = Not provided, therefore, the default value will be used.
*/
// CLI
$ whoami && php script.php --params=foo/bar
housni // foo/bar
[os] =>
[username] => housni
[env] =>
]
// HTTP
script.php?params=foo/bar
Array
[
[params] => foo/bar
[os] =>
// The username of my Apache user, the result of posix_getpwuid[posix_geteuid[]]['name']
[username] => www-data
[env] =>
]
As you can see, the output is consistent when the script is executed via the CLI or the web.
uberlinuxguy at tulg dot org ¶
14 years ago
One thing of important note would be that getopt[] actually respects the '--' option to end an option list. Thus given the code:
test.php:
And running:
# ./test.php ./run_vfs -h test1 -g test2 -m test3 -- this is a test -m green
Will return:
Array
[
[h] => test1
[g] => test2
[m] => test3
]
Whereas running:
# /test.php ./run_vfs -h test1 -g test2 -m test3 this is a test -m green
Will return:
Array
[
[h] => test1
[g] => test2
[m] => Array
[
[0] => test3
[1] => green
]
]
Francois Hill ¶
14 years ago
Although very interesting, koenbollen at gnospamail dot com's update of the argv array fails when option values follow the option with no space :
Indeed
php MyScript.php5 -t5
and
php MyScript.php5 -t 5
with $options="t:" are treated as the same by getopt.
This upgraded function should take care of it :
File : shift_test.php5
>php shift_test.php5 -h -t4 param1 param2
will ouptut :
Array
[
[0] => test.php5
[1] => -h
[2] => -t4
[3] => param1
[4] => param2
]
Array
[
[0] => test.php5
[1] => param1
[2] => param2
]
>php shift_test.php5 -h -t 4 param1 param2
will ouptut :
Array
[
[0] => test.php5
[1] => -h
[2] => -t
[3] => 4
[4] => param1
[5] => param2
]
Array
[
[0] => test.php5
[1] => param1
[2] => param2
]
joey at alegria dot co dot jp ¶
16 years ago
There are 2 simpler [and much faster] methods for getting good getopt[] operation without creating your own handler.
1. Use the Console_Getopt PEAR class [should be standard in most PHP installations] which lets you specify both short and long form options as well as whether or not arguments supplied to an option are themselves 'optional'. Very simple to use and requires very little code to operate compaired to writing own handler.
2. If you cannot load external PEAR objects, use your shell's getopt[] functions [which in BASHs case work very well] to process options and have your shell script then call your PHP script with a rigid argument structure that is very easy for PHP to digest such as:
% myfile.php -a TRUE -b FALSE -c ARGUMENT ...
If the initial arguments are invalid you can have the shell script return an error without calling the PHP script. Sounds convoluted but is a very simple solution and in fact PHP's own % pear command uses this method. /usr/bin/pear is a shell script that does some simle checking before calling pearcmd.php and repassing the arguments on to it.
The second method is by far the best for portability because it allows a single shell script to check a few things like your PHP version and respond acordingly e.g. does it call your PHP4 or PHP5 compatible script? Also, because getopt[] is not available on Windows, The second solution allows you to do Windows specific testing as a BAT file [as oposed to BASH, ZSH or Korn on UNIX].
mbirth at webwriters dot de ¶
14 years ago
After getopt[] of PHP5.3.0 [on Windows] ignored some parameters if there was a syntactical problem, I decided to code my own generic parameter parser.
A call like: php.exe -f test.php -- alfons -a 1 -b2 -c --d 2 --e=3=4 --f "alber t" hans wurst
and an in-program call parseParameters[array['f']]; would yield in a resulting array:
Array
[
[0] => alfons
[a] => 1
[b2] => 1
[c] => 1
[d] => 2
[e] => 3=4
[f] => 1
[1] => alber t
[2] => hans
[3] => wurst
]
As you can see, values without an identifier are stored with numeric indexes. Existing identifiers without values get "true".
mpartap at gmx dot net ¶
11 years ago
Here's another way of removing options found by getopt[] from the argv[] array. It handles the different kind of parameters without eating chunks that do not belong to an --option. [-nr foo param1 param2 foo]
taka8aru at gmail dot com ¶
2 years ago
getopt[] simply ignores unnecessary options specified in argv.
Many times, it does not work well to handle errors in command line.
A package PEAR::Console_Getopt can handle this problem, but it requires additonal installation.
GNU getopt[1] does well at shell level.
Following is my extended getopt[] can detect unnecessary options:
Damien B. ¶
14 years ago
This is how I handle arguments with getopt: I use switch within a foreach at the beginning of a program.
koenbollen at gnospamail dot com ¶
15 years ago
After you use the getopt function you can use the following script to update the $argv array:
Note: I used the array_merge function to reindex the array's keys.
Cheers, Koen Bollen
takingsides at gmail dot com ¶
8 years ago
As already mentioned getopt[] will stop parsing options upon the '--'. Sometimes you will have options and arguments but the user may not always provide the explicit -- option.
Below is a quick way to collect options and arguments regardless of the -- consistently.
#!/usr/bin/php
geoff at gosquared dot com ¶
12 years ago
It seems under PHP 5.3.2, getopt[] makes a script fail to load if called via HTTP without any conditions. You'll need something like if[isset[$_SERVER['argc']]] $args = getopt[]; to prevent that.
Anonymous ¶
15 years ago
About getopt[String]:
Parses the command-line arguments into an associative array, using the function's String parameter to specify arguments and options, thus:
* arguments are specified as any letter followed by a colon, e.g. "h:".
* arguments are returned as "h" => "value".
* options are specified as any letter not followed by a colon, e.g. "r".
* options are returned as "r" => [boolean] false.
Also note that:
1] Options or arguments not passed in the command-line parameters are not set in the returned associative array.
2] Options or arguments present in the command-line arguments multiple times are returned as an enumerated array within the returned associative array.
S2 ¶
1 month ago
As noted the options not required or optional [parameter does not accept any value] only returns the index key with a value of FALSE when provided as an argument. That is counter-intuitive to how the option will likely be used, so simply leverage the keys existence and reset the variable's index for that option:
shell> php testfile.php --insert
array[2] {
["update"]=>
bool[false]
["insert"]=>
bool[true]
}
Dominik Deobald ¶
7 months ago
This documentation never really explains the logic behind $short_options and just expects that you get it from reading the examples.
So if you are like me and start to think that the order of letters between the ":" characters has anything to say, think simpler.
It really is...
- every letter in the string will be allowed as a parameter,
- if that letter has ONE colon after it, then it will require a value
- if it has TWO colons, then it can accept a value
- the order of the letters does not matter at all as long as the colons are where they belong.
That means that these two examples are the same: "ab::c:def:" "adec:f:b::"
gingko at gingko dot ovh ¶
1 year ago
Unfortunately, even using Example #4 do not allow to easily detect a bad -x or --xx argument as the last -x or --xx is always “eaten” even if it is bad:
If I use this [Example #4] :
shell> php example.php -a 1 -b 2
shell> php example.php -a 1 -b 2 --test
shell> php example.php -a 1 -tb 2
All return the same result [-t and --test not defined] :
array[0] {
}
[last one use combining single letters, making user testing much much more complicated]
edg at Greenberg dot org ¶
1 year ago
> This function will return an array of option / argument pairs, or false on failure.
I note that on my PHP 7.4 installation, getopt returns an empty array for no options specified, not FALSE as the doc states. Although "failure" is rather non-specific. Maybe that doesn't include the condition of no options.
micropresident at gmail dot com ¶
6 years ago
when using -f option to indicate script name, php does not allow to use double dash -- to define options after the script name;
For example, the following command cannot be execute:
php -f myscript.php --config "myconfig.ini"
rastyazhenko dot anton at gmail dot com ¶
2 years ago
$opts = getopt['', $params = ['ogrn:','inn:','kpp::','host:','port:','user:','pass:','path:','pattern:']] + ['kpp' => 0,'port' => 21,'path' => '/','pattern' => '.+\.dbf'];
array_map[function [$param] use [$opts] {
$matches = [];
if [[bool]preg_match['/[?[^:\s]+]\b:$/sU', $param, $matches]
&& [!array_key_exists[$matches['param'], $opts] || empty[$opts[$matches['param']]]]]
die[sprintf['1%s not set', $matches['param']]];
}, $params];
salimzadehsajad at gmail dot com ¶
5 years ago
if you use command like below
php [filename] [argument without [-] ] [options]
getopt don't return value. you can use this function
function getoptions[] {
global $argv,$argc;
$options = array[];
for[$i = 0;$i < $argc;$i++] {
$arg = $argv[$i];
if[strlen[$arg] > 1 && $arg[0] == '-'] {
if[$arg[1] == '-' && $i + 1 < $argc] { $i++; $options[substr[$arg,2,strlen[$arg]]] = $argv[$i]; }
else $options[$arg[1]] = substr[$arg,2,strlen[$arg]];
}
}
return $options;
}
wouter dot berben at phpro dot be ¶
5 years ago
Your description on getopt is either wrong or the documentation of the function is wrong.
-- snippet --
array getopt [ string $options [, array $longopts [, int &$optind ]] ]
--
As I read this only the first parameter string $options is required.
-- snippet --
longopts
An array of options. Each ...
optind
If the optind parameter is present, ...
--
This means that "longopts" is optional, but the third parameter "optind" is required [although the description leaves room for interpretation]. This is against the possibilities of PHP because when a parameter is declared optional all following parameters must be declared optional as well.
See //php.net/manual/en/functions.arguments.php Example #4 and #5.
The immutable embedded stub [PHPStorm] [ //github.com/JetBrains/phpstorm-stubs/blob/master/standard/standard_3.php ] specifies this:
-- snippet --
function getopt [$options, array $longopts = null, &$optind] {}
--
Which is also wrong, but probably based upon this documentation.