Hướng dẫn what is php cli command? - lệnh php cli là gì?

16 tháng 9 tại PSU DOT EDU ¶

10 năm trước

You can easily parse command line arguments into the $_GET variable by using the parse_str[] function.



It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

Ẩn danh ¶

1 năm trước

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal:

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.

Apmuthu tại USA DOT NET

4 năm trước

Adding a pause[] function to PHP waiting for any user input returning it:



It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

0

notrealllyanaddress tại Somerandomaddr dot com ¶

12 năm trước

[implode['&', array_slice[$argv, 1]], $_GET];?>

It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

2

[implode['&', array_slice[$argv, 1]], $_GET];?>

It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

3

Sam Marshall ¶

3 năm trước

[implode['&', array_slice[$argv, 1]], $_GET];?>

It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

5

[implode['&', array_slice[$argv, 1]], $_GET];?>

It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

6

[implode['&', array_slice[$argv, 1]], $_GET];?>

It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

7

[implode['&', array_slice[$argv, 1]], $_GET];?>

It behaves exactly like you'd expect with cgi-php.

$ php -f somefile.php a=1 b[]=2 b[]=3

This will set $_GET['a'] to '1' and $_GET['b'] to array['2', '3'].

Even better, instead of putting that line in every file, take advantage of PHP's auto_prepend_file directive.  Put that line in its own file and set the auto_prepend_file directive in your cli-specific php.ini like so:

auto_prepend_file = "/etc/php/cli-php5.3/local.prepend.php"

It will be automatically prepended to any PHP file run from the command line.

8

Psikyo tại mail dot dlut dot edu dot cn ¶

9 năm trước

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
0

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
1

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
2

ben tại slax0rnet dot com

18 năm trước

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
4

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
5

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
6

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
7

We can pass many arguments directly into the hashbang line.
As example many ini setting via the -d parameter of php.
---
#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0
phpinfo[];
exit;
---
./script | grep memory
memory_limit => 2048M => 2048M
---
But we can also use this behaviour into a second script, so it call the first as an interpreter, via the hashbang:
---
#!./script arg1 arg2 arg3
---
However the parameters are dispatched in a different way into $argv
8

Kodeart ¶

11 năm trước

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.0

Overflow636 tại Gmail Dot Com ¶

17 năm trước

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.1

Franknospamwanted tại. Toppoint Dot. de ¶

7 năm trước

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.2

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.3

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.4

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.5

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.6

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.7

Ẩn danh ¶

12 năm trước

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.8

Sam Marshall ¶

15 năm trước

All the parameters are in $argv[1], $argv[0] is the interpreter script name, and $argv[1] is the caller script name.9

Monte at ispi dot net ¶

17 năm trước

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 0

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 1

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 2

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 3

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 4

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 5

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 6

Franknospamwanted tại. Toppoint Dot. de ¶

19 năm trước

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 8

To get back the parameters into $argv, we can simply test if $argv[1] contains spaces, and then dispatch again as normal: 9

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
0

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
1

OHCC tại 163 dot com ¶

6 năm trước

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
3

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
4

notrealllyanaddress tại Somerandomaddr dot com ¶

15 năm trước

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
6

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
7

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
8

Monte at ispi dot net ¶

15 năm trước

#!/usr/bin/php -d memory_limit=2048M -d post_max_size=0

---
array[3] {
  [0]=>
  string[8] "./script"
  [1]=>
  string[15] "arg1 arg2 arg3 "
  [2]=>
  string[14] "./other_script"
}
array[4] {
  [0]=>
  string[8] "./other_script"
  [1]=>
  string[4] "arg1"
  [2]=>
  string[4] "arg2"
  [3]=>
  string[4] "arg3"
}
---
This will maintain the same behaviour in all cases and allow to even double click a script to call both parameters of another script, and even make a full interpreter language layer.  The other script doesn't has to be php. Take care of paths.
9

0

1

2

Monte at ispi dot net ¶

15 năm trước

4

5

6

7

Monte at ispi dot net ¶

19 năm trước

8

9

Adding a pause[] function to PHP waiting for any user input returning it:0

Adding a pause[] function to PHP waiting for any user input returning it:1

OHCC tại 163 dot com ¶

15 năm trước

Adding a pause[] function to PHP waiting for any user input returning it:3

Adding a pause[] function to PHP waiting for any user input returning it:4

Adding a pause[] function to PHP waiting for any user input returning it:5

Adding a pause[] function to PHP waiting for any user input returning it:6

Monte at ispi dot net ¶

18 năm trước

Adding a pause[] function to PHP waiting for any user input returning it:8

Adding a pause[] function to PHP waiting for any user input returning it:9

Kodeart ¶

17 năm trước

Bài Viết Liên Quan

Chủ Đề