Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17251 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63142 invoked by uid 1010); 13 Jul 2005 03:17:24 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 63127 invoked from network); 13 Jul 2005 03:17:24 -0000 Received: from unknown (HELO gmail.com) (127.0.0.1) by localhost with SMTP; 13 Jul 2005 03:17:24 -0000 X-Host-Fingerprint: 64.233.162.198 zproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.162.198:39843] helo=zproxy.gmail.com) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id D0/13-23681-3C784D24 for ; Tue, 12 Jul 2005 23:17:23 -0400 Received: by zproxy.gmail.com with SMTP id x3so54104nze for ; Tue, 12 Jul 2005 20:17:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iv7EQSBv5N9fdt/22dXe7xVGlSZlDkasepjRJr3Bq6AGckW06Pzo9v6fZWbpSul69LXrmEu49JGDqSdC6QljL4n4q4rsTHfPdrSBb3RBHLIjdpVJWeibuhhQoEDlAA05flshu7jX+kBPewiseGrxMjrBIFNmoPpZtuAehSQRXoc= Received: by 10.36.39.7 with SMTP id m7mr419674nzm; Tue, 12 Jul 2005 20:17:21 -0700 (PDT) Received: by 10.36.104.12 with HTTP; Tue, 12 Jul 2005 20:17:21 -0700 (PDT) Message-ID: <90e24d4e050712201753788494@mail.gmail.com> Date: Tue, 12 Jul 2005 20:17:21 -0700 Reply-To: Jeremy Johnstone To: Chuck Hagenbuch Cc: internals@lists.php.net In-Reply-To: <20050712161703.rf2hn68dptcswssw@marina.horde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050712105234.5dhkvvd6ghcsw8sg@marina.horde.org> <20050712212026.5bd2dbbb.pierre@dotgeek.org> <42D42430.5060001@prohost.org> <20050712161703.rf2hn68dptcswssw@marina.horde.org> Subject: Re: [PHP-DEV] php 4.4 BC break From: phpdev@gmail.com (Jeremy Johnstone) On 7/12/05, Chuck Hagenbuch wrote: > Yes, they could turn off warnings. But since the code has always run > cleanly beforehand, they don't think to do that. It's definitely not the cleanest solution, but for those of you who want to have a "quick fix" which will hide the problem until you have time to fix it properly, use the following at the top of a common file: if(!defined('E_STRICT')) { define('E_STRICT', 2048); } error_reporting(error_reporting() & ~E_NOTICE & ~E_STRICT); Never depend on a user to do something for you that you can do yourself. If you feel notice reporting should be off on a production level script, then turn them off, and make it easy and documented for them to turn it back on if they want it, not expect them to know how to disable them theirself automatically. --=20 --------------------------- Jeremy Johnstone http://www.jeremyjohnstone.com jsjohnst@php.net