Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23442 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38378 invoked by uid 1010); 16 May 2006 03:58:52 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 38363 invoked from network); 16 May 2006 03:58:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 May 2006 03:58:51 -0000 X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 192.38.9.232 gw2.emini.dk Linux 2.4/2.6 Received: from ([192.38.9.232:1554] helo=gw2.emini.dk) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 4F/01-19568-AFD49644 for ; Mon, 15 May 2006 23:58:50 -0400 Received: from foxbox (unknown [84.228.79.24]) by gw2.emini.dk (Postfix) with ESMTP id A476CB1B9C; Tue, 16 May 2006 05:58:46 +0200 (CEST) Message-ID: <093301c677d3$9c86e9d0$6602a8c0@foxbox> Reply-To: "Steph Fox" To: "Brian Moon" , , "Andi Gutmans" References: <138663365.20060514205903@marcus-boerger.de><038d01c676f8$ab9b3380$6602a8c0@foxbox><44685D24.2000801@php.net><1408277471.20060515204040@marcus-boerger.de><083d01c67786$96d5b9f0$6602a8c0@foxbox><4468CD27.4010608@dealnews.com> <7.0.1.0.2.20060515191951.03913ec0@zend.com> Date: Mon, 15 May 2006 05:56:55 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PHP-DEV] E_ALL changes in 5.2/6.0 From: steph@zend.com ("Steph Fox") At 11:49 AM 5/15/2006, Brian Moon wrote: >>Perhaps there should be an ini-development and an ini-production. > > "recommended" was born after "dist" because we wanted to show how to run > PHP correctly (esp. BC breaking INI parameters such as > register_globals=off which are recommended). It's a bit different from > development vs. production which I agree would be very helpful. Question > is how do we do it? Do we abandon the former for the latter, or is there a > way to solve all at once? :) Andi, if you go back and actually read those files they claim to be 'default settings' and 'production settings' respectively. I agree the whole idea of 'default settings' should be dropped (in this sense), but I think you'll find most people out there take those directives as 'how PHP should be used'. To me it's a tad worrying - given that context - that the error_reporting recommendations are as they are. Since both files are being, if you like, 'marketed' in the way Brian mentioned, it might be a good time to a) rename them in the way he suggested and b) go through those settings with a fine-toothed comb before doing so. Just an opinion, of course... - Steph