Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62796 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64753 invoked from network); 4 Sep 2012 13:51:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2012 13:51:03 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.160.42 mail-pb0-f42.google.com Received: from [209.85.160.42] ([209.85.160.42:58540] helo=mail-pb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 03/53-46870-74706405 for ; Tue, 04 Sep 2012 09:51:03 -0400 Received: by pbbrp8 with SMTP id rp8so9356197pbb.29 for ; Tue, 04 Sep 2012 06:51:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H/k+g2MCX+GfrZ6EE9VoKUuv4ddekRDlOXFNs897rTQ=; b=hqBa7pHU3TdIS6r1awI7L0b+iWEHZs7WE4Coa3JHu/Zrld8fCalp5jIu3zrD2cxTOE QsioH4vmZ2sNjnGZ3kHvKwLVTWV8v4NM9CyMU8I6SxA54yp2MFI+lbC8ul0qDWIRvTM3 YHvuZGwS5u+ebIYGxPz7DORQeZbfSFpsgLIZPqLBgAAuDo1v9V1wMBOmmHZUUrBt64PI bJi3Sdz1ZaJa74ALDnJQ2X44+IluHvpblS/+tpDZMo7BbzeNfEfTl02+M71sH4sKKRVw dNSL7haMfkxZ2dahfXKPBUJmcGC0HGYOFM8Pkq19UG/3WEkLt70gahMe5YK3N5oRQ8nf hiBA== MIME-Version: 1.0 Received: by 10.66.83.8 with SMTP id m8mr41358348pay.48.1346766659980; Tue, 04 Sep 2012 06:50:59 -0700 (PDT) Received: by 10.68.211.37 with HTTP; Tue, 4 Sep 2012 06:50:59 -0700 (PDT) In-Reply-To: <504605A5.3000600@lsces.co.uk> References: <5040F4D9.80206@sugarcrm.com> <5042946A.80204@sugarcrm.com> <5042A7D6.7050001@lerdorf.com> <50452713.3020307@sugarcrm.com> <5045CAA3.6000409@lsces.co.uk> <5045E044.9080809@lsces.co.uk> <5045F939.6010806@lsces.co.uk> <5045FD98.8080306@lsces.co.uk> <504605A5.3000600@lsces.co.uk> Date: Tue, 4 Sep 2012 15:50:59 +0200 Message-ID: To: Lester Caine Cc: PHP internals Content-Type: multipart/alternative; boundary=f46d042ef4675d0ca904c8e08cd0 Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core? From: tyra3l@gmail.com (Ferenc Kovacs) --f46d042ef4675d0ca904c8e08cd0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > > > Using third party code - joomla - only difference between working and not > working is switching E_STRICT on. With display_errors=3Doff one gets a wh= ite > screen. I was not surprised as I've had this all the way through with cod= e > from many sources. Yes a lot of the time you just get the error messages, > but a white screen crash has been the norm most of the time so leaving > display_errors=3Don helps while fault finding on the development systems. > > usually most people set display_errors=3Doff but log_errors =3D on and just check the logfiles for errors. there is no point bothering your users with messages they won't understand or could be able to do anything about, plus it is usually a security vulnerability (Information Leakage). --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --f46d042ef4675d0ca904c8e08cd0--