Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83794 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64646 invoked from network); 25 Feb 2015 15:10:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2015 15:10:43 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.179 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.179 mail-wi0-f179.google.com Received: from [209.85.212.179] ([209.85.212.179:64909] helo=mail-wi0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/84-62407-3F5EDE45 for ; Wed, 25 Feb 2015 10:10:43 -0500 Received: by mail-wi0-f179.google.com with SMTP id ex7so5788597wid.0 for ; Wed, 25 Feb 2015 07:10:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=B2rlTLUKmR6ybfLG8L7CtXdF61lE8HIcyCyiJHZuu1Q=; b=gXsHyif04EKuDEqf1/f7W0MddPJeGSWQxCoKzm1g5QJye6gg7MzNUApTZReZ/xx3QL GgIh6mkVdSoUHd+4/JzLLSJTqSJYYGMo3MoIJjukuThAuKfr0pip7Tb8VwGpTrzvty2z f2lPARPZNKR2lVaJF2a/ajLd2qjb6GWiyElIFGA50qujUjAKU3dkjBSw3+OUHKEm1X1V YXX+7xOeuEbvgnFSV9PRGQHd0IDBgN0nb52L0rsgoofRacZj3zbogdDMJVt0rjdwjy4z IZ9vxx/v3o4sauChZeYf0ShZy6ALFBoNx71NLIOAPAY4IAGrLCpv+8SxMlYN8DKEilS+ uBng== X-Received: by 10.194.103.228 with SMTP id fz4mr7073313wjb.82.1424877039696; Wed, 25 Feb 2015 07:10:39 -0800 (PST) Received: from [192.168.0.136] ([62.189.198.114]) by mx.google.com with ESMTPSA id s5sm29972220wia.1.2015.02.25.07.10.38 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Feb 2015 07:10:38 -0800 (PST) Message-ID: <54EDE5D8.2010303@gmail.com> Date: Wed, 25 Feb 2015 15:10:16 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Dmitry Stogov CC: PHP Internals References: <54E12349.7070806@gmail.com> <16.9B.05176.AE1C1E45@pb1.pair.com> <54E1C993.1070609@gmail.com> <37.20.01961.31113E45@pb1.pair.com> <54E32CAA.5030600@gmail.com> <54E4FAC2.7060200@gmail.com> <47.89.25547.DD007E45@pb1.pair.com> <54EDCBD6.70302@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine From: rowan.collins@gmail.com (Rowan Collins) Dmitry Stogov wrote on 25/02/2015 14:07: > No. The proposal is only about fatal engine errors, like "Fatal Error: > Call to undefined function %s()". > Instead of script termination they will throw exceptions. > fopen() won't be touched at all. It's out of scope of proposal. Hi Dmitry, I was responding to a sub-thread where Tony Marston was requesting it be extended to other scenarios, and explaining why the idea of changing behaviour based on context would not work. I agree that the current proposal, for fatal errors only, does not constitute a significant BC break, particularly if the BaseException superclass is added. Regards, -- Rowan Collins [IMSoP]