Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110862 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 55721 invoked from network); 7 Jul 2020 16:09:57 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 7 Jul 2020 16:09:57 -0000 To: internals@lists.php.net References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com> <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com> Date: Tue, 7 Jul 2020 16:00:39 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 87.81.129.66 Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics From: marandall@php.net (Mark Randall) Message-ID: On 07/07/2020 15:46, Larry Garfield wrote: > This has reached the 2 week mark, but there's not been much discussion. Anyone else want to weigh in? We wanted to add that, general sentiment seems to be moving towards using Exceptions for communicating errors, potentially including a large effort towards it for 8.1. This would mean that each extension would likely need to add many of its own exception classes to build up a full hierarchy, all of which, in the current setup, would go into root. With this RFC passed we could realistically expect them to be placed into their respective namespaces keeping the whole thing much more self contained and tidy. Mark Randall