Re: "forced" ini settings in CLI don't work anymore..
| From: | (Marcus Börger) | Date: | Sat, 19 Apr 2003 17:40:56 +0000 |
| Subject: | Re: "forced" ini settings in CLI don't work anymore.. | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-980@lists.php.net to get a copy of this message | ||
At 01:33 18.04.2003, Jani Taskinen wrote:
On Wed, 16 Apr 2003, Marcus Börger wrote: At 05:03 16.04.2003, Jani Taskinen wrote:It is more likely that you use an ini file that is not appropriate, means we have to add more ini defaults in run-tests.php. For me everything is just fine whether that implicit_flush is On or Off doesn't make a difference for me. marcusThey 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).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?You effectively broke BC with this change.See the ext/pcntl/tests/001.phpt which now fails because of this. It assumes implicit_flush is always 'On' as it only runs in CLI. I would guess some other people have made the same assumption..The settings were "hardcoded" for CLI for a reason, so please make these behave like they did before.