Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81302 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34679 invoked from network); 28 Jan 2015 11:21:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2015 11:21:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.52 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.218.52 mail-oi0-f52.google.com Received: from [209.85.218.52] ([209.85.218.52:56467] helo=mail-oi0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DD/EE-45774-746C8C45 for ; Wed, 28 Jan 2015 06:21:45 -0500 Received: by mail-oi0-f52.google.com with SMTP id h136so17010300oig.11 for ; Wed, 28 Jan 2015 03:21:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=wcJnGHyEJKl1BeR1FoJ1Tu+2y+D93ZD8ZOcCAgp8ygI=; b=q7O4EwIie41sL6mwN+QDmej4TobPQ8jiDMTMH3wTwGM5csk8kxwGEUJs1TBknZbSzy lOr8NnYkfU1SCTukNoxB2u0MxHf1jlJvJgdqQL+q+OCZ9nFm1+q+gCbstzI5oEqB8B/O 0zpj/GZ9OnpmDkurntNVaMM+wFkzIx7yoQzsJmGBXSiFLKkOaMX5fcRL5LAFgYQSWlq2 y8VLopZvfZZdLO47udkDOogSm/XfcaJ435xVDEFX4uG+q/Itn8LndtIgiDXp1iQWHsyX GFSn89SjwjVZ4ZcC36jzhrxy453sv+QvKIC+tn1Za6H1XZC4NCKrjEYzJip82XEFop55 x6tw== X-Received: by 10.202.18.11 with SMTP id 11mr1591434ois.61.1422444100729; Wed, 28 Jan 2015 03:21:40 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.202.229.9 with HTTP; Wed, 28 Jan 2015 03:21:00 -0800 (PST) In-Reply-To: <54C8BE99.8070109@gmail.com> References: <54C80F4F.7020905@gmail.com> <011d01d03ab7$dd725c30$98571490$@tekwire.net> <54C8BE99.8070109@gmail.com> Date: Wed, 28 Jan 2015 20:21:00 +0900 X-Google-Sender-Auth: dftp-u_uZhN0-MeYeBUKmKOeW8Y Message-ID: To: Rowan Collins Cc: PHP Internals Content-Type: multipart/alternative; boundary=001a113d15ae56436c050db493e9 Subject: Re: [PHP-DEV] Proposal: Raise severity of undefined constants From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a113d15ae56436c050db493e9 Content-Type: text/plain; charset=UTF-8 Hi Rowan, On Wed, Jan 28, 2015 at 7:48 PM, Rowan Collins wrote: > On the other hand, if the concern is having to support it, then it could > just be E_ERROR. The reason I chose E_RECOVERABLE_ERROR is because that had > recently been adopted for other things, such as invalid method calls. As I > mentioned in my original e-mail, the recovery behaviour needn't be the > existing string interpretation, but could just be to treat the value as > NULL, which would probably be simpler to implement. Personally, I've never > actually recovered an E_RECOVERABLE_ERROR, so am not sure what use cases we > should be supporting. Please don't use E_ERROR. It cannot be catched by user error handler now. If user error handler can catch it, then I don't mind it. E_RECOVERBLE_ERROR is better than E_ERROR. I use user defined error handler always for immediate notification. I use log analyzer also, but it has time lag. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a113d15ae56436c050db493e9--