Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62805 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92138 invoked from network); 4 Sep 2012 17:24:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2012 17:24:34 -0000 Authentication-Results: pb1.pair.com header.from=simpleshot@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=simpleshot@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender) X-PHP-List-Original-Sender: simpleshot@gmail.com X-Host-Fingerprint: 209.85.210.170 mail-iy0-f170.google.com Received: from [209.85.210.170] ([209.85.210.170:50305] helo=mail-iy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5E/78-46870-15936405 for ; Tue, 04 Sep 2012 13:24:33 -0400 Received: by iamm10 with SMTP id m10so10473277iam.29 for ; Tue, 04 Sep 2012 10:24:31 -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 :content-type; bh=QXB7WeYsLzAkO7knPDmh+dCocuv392RxdT+xhATEbmc=; b=tQh2ESvbINQMa/MmOQNvkBE6IDxyEcarpDAfHGsP8uDPorYlRZxGylslsvepj4Cnmh weZ4KiITu2va4Z0BefiAlMWfppDXoQp5m99v8qMs8nw0QT1K4D1cAwOWluHZ0fja6pyl r11bkw5Lczh3T4WjG+8G135MT4I+kw/7k8A8jahSZgCRyznDEaxaJwbEqA/RI+0FEnKq nVktAec1O9SxJtnIgeY0SYw/1HMJ5F6xVycS+v2sngbZ9sKcFXqEigcG1lwKdaUL8swH 5e0BSNDKQoWJ4jZICjCcogknvPf3mr7WXArGmD8Qt8JWhiRO+1okYDuOTztKKFiacp+T yJ6Q== MIME-Version: 1.0 Received: by 10.60.22.169 with SMTP id e9mr9704169oef.124.1346779470874; Tue, 04 Sep 2012 10:24:30 -0700 (PDT) Received: by 10.60.118.167 with HTTP; Tue, 4 Sep 2012 10:24:30 -0700 (PDT) In-Reply-To: <50463317.7000109@lerdorf.com> References: <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> <50463317.7000109@lerdorf.com> Date: Tue, 4 Sep 2012 13:24:30 -0400 Message-ID: To: PHP Development Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core? From: simpleshot@gmail.com (Adam Richardson) On Tue, Sep 4, 2012 at 12:57 PM, Rasmus Lerdorf wrote: > Only on a new E_STRICT. Even with E_STRICT off by default, custom error > handlers are still called, and I think Lester said that turning E_STRICT > off made it work. So if this is the cause, then it has nothing to do > with E_STRICT being in E_ALL or not, nor whether display_errors is on or > off. It would have to do with the custom error handler blowing up on one > specific E_STRICT, which I find rather unlikely. > > -Rasmus Whoops, you're right! I forgot that the custom error handler is called regardless of error reporting. Adam -- Nephtali: A simple, flexible, fast, and security-focused PHP framework http://nephtaliproject.com