Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62804 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84230 invoked from network); 4 Sep 2012 16:58:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Sep 2012 16:58:07 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.216.42 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.216.42 mail-qa0-f42.google.com Received: from [209.85.216.42] ([209.85.216.42:34619] helo=mail-qa0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DE/B6-46870-E1336405 for ; Tue, 04 Sep 2012 12:58:07 -0400 Received: by qaeb19 with SMTP id b19so3503375qae.8 for ; Tue, 04 Sep 2012 09:58:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=8S7MbP+AtjvOjHr0Rupm/ziJfep7EBt5PTWLYtdb7U4=; b=H3B67gMng8WmYPe/TOTkP6Goq73RfMLVcyeGcNRYSKkyQJ7ebBb10u/Jsb7Ioe4176 csrQQ1GORymN4qh40MHM4e+kBvOpkZlC72iycWZffqu8M3vNOCKDGIaIhDrfTDYhrck2 5QuuawVDjFuH32zrmYjvAN8d0R4eCvOVKgn5/ErRX09duAwxB9LvUsScS3596CXfATip qvQR0AM24tMsLM6fdzr2F0m8r/jd1mmvrusfGRduYs6Xrh81bC9GtK9kMGA8vCqKUiRM WyP6THyI17heqC2N6upK0uD/Q3DB8T+ZaSyi2X85EEvnoSLSMLom/eJNy45/lOS+ReuH HwIA== Received: by 10.224.199.135 with SMTP id es7mr41113173qab.6.1346777883177; Tue, 04 Sep 2012 09:58:03 -0700 (PDT) Received: from [192.168.200.148] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPS id dg10sm15128922qab.12.2012.09.04.09.58.01 (version=SSLv3 cipher=OTHER); Tue, 04 Sep 2012 09:58:01 -0700 (PDT) Message-ID: <50463317.7000109@lerdorf.com> Date: Tue, 04 Sep 2012 09:57:59 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Adam Richardson CC: PHP Development 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> In-Reply-To: X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnhSCwsczRIgfmY/CRNlc/J/y/C+lK6/4zeh6rcyK0JPcr03aZHuQTB7ffW4v6dRM8Edza8 Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core? From: rasmus@lerdorf.com (Rasmus Lerdorf) On 09/04/2012 09:36 AM, Adam Richardson wrote: > I think Ferenc is correct in that this sounds like there's a custom > error handler somewhere. If the custom error handler collects error > info and then throws an exception (as has been detailed in various > blog posts as one manner of unifying the errors), this would cause the > trouble you're seeing. 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