Re: Re: RFC for new INI's
| From: | Ilia Alshanetsky | Date: | Wed, 11 Feb 2009 14:33:19 +0000 |
| Subject: | Re: Re: RFC for new INI's | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-42994@lists.php.net to get a copy of this message | ||
On 11-Feb-09, at 9:26 AM, Christian Schneider wrote:
Eric Stewart wrote:I think it makes sense to have it on in both.A new RFC for PHP's proposed INI files have been added to the wiki. Below is a direct link to the page. http://wiki.php.net/rfc/newinisGood work IMHO. Similar to what Karsten Dambekalns wrote I think we should only have a difference between devel and production for display/logging options, but not for options changing the 'behaviour' of PHP. So I'd propose allow_call_time_pass_reference = Off (devel) / On (production) display_errors = On (devel) / Off (production) display_startup_errors = On (devel) / Off (production) html_errors = On (devel) / Off (production) session.bug_compat_warn = On (devel) / Off (production) track_errors = On (devel) / Off (production) but output_buffering = 4096 ; Changes header()/compression filter behaviour
register_argc_argv = Off ; Why should devel have access if prod doesn't?off in both.
request_order = GPCS ; Why should devel/production differ? session.bug_compat_42 = Off ; Why should devel/production differ?Agreed. Ilia Alshanetsky