unread
Apparently the changes you made to cleanup the ini settings
forcing in CLI do not work as expected:
<?php
var_dump(ini_get('register_argc_argv'));
var_dump(ini_get('html_errors'));
var_dump(ini_get('display_errors'));
var_dump(ini_get('implicit_flush'));
var_dump(ini_get('max_execution_time'));
?>
Results with CLI build before the changes were merged:
string(1) "1"
string(1) "0"
string(1) "1"
string(1) "1"
string(1) "0"
Results with latest CVS checkout (PHP_4_3 branch):
string(1) "1"
string(1) "0"
string(1) "1"
string(0) ""
string(2) "30"
When '-n' is used (to not use any php.ini) both builds work fine.
So, are these not supposed to be forced defaults anymore for CLI?
--Jani
unread
At 05:03 16.04.2003, Jani Taskinen wrote:
>
> When '-n' is used (to not use any php.ini) both builds work fine.
> So, are these not supposed to be forced defaults anymore for CLI?
>
They only overwrite the settings for -n now. The key idea was
that the user should be able to change the values by all three
mechanisms: "-d" option, php-cli.ini and `ini_set()`. If there
were any ini setting that really needed to overwrite the ini
file always we could do that, too (but i don't see a need for it).
marcus
>
> When '-n' is used (to not use any php.ini) both builds work fine.
> So, are these not supposed to be forced defaults anymore for CLI?
>
They only overwrite the settings for -n now. The key idea was
that the user should be able to change the values by all three
mechanisms: "-d" option, php-cli.ini and `ini_set()`. If there
were any ini setting that really needed to overwrite the ini
file always we could do that, too (but i don't see a need for it).
marcus