Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69901 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43502 invoked from network); 27 Oct 2013 16:11:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Oct 2013 16:11:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.46 mail-wg0-f46.google.com Received: from [74.125.82.46] ([74.125.82.46:61957] helo=mail-wg0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F3/2D-45431-D3B3D625 for ; Sun, 27 Oct 2013 11:11:42 -0500 Received: by mail-wg0-f46.google.com with SMTP id m15so5551631wgh.13 for ; Sun, 27 Oct 2013 09:11:39 -0700 (PDT) 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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=foNL2nZiR9Tb7oGOEhjTLKPR5SPyJKKkfySYXFQOJp8=; b=UibEklV5U7YOHyIugWL/Fw/HFRv8pKV/jCb/YtT3kA1KLGEcXud1C3RLLO9WZuehMF ZtFXNcN4klJBxm5LlguZRofi63KCFkSHgS/I4VdxanAXz70FUGWrYcEKt+xb0XmtUef7 EYK6FWZg2e/8JGE8VSWOwFDvqKNSKqs+PkgZ9NNV3zhIxHEzLX2riRzKu8XL4LS3Sevo Zh4KXgzbWJUgBOEDhE2+dcrTl6ZNfG6kfd05ZSSn5rcDgzt1sgMJ/6R9ejhBOg4OIl8p v+XUmKx8UBcfJiqgIemACb2EgOiPDhw6pJbBo0WQXJHEMrLqFGlW8apvshU9DEHFHIIU oN3Q== X-Received: by 10.180.9.139 with SMTP id z11mr5777849wia.22.1382890299106; Sun, 27 Oct 2013 09:11:39 -0700 (PDT) Received: from [192.168.0.2] (cpc19-brig17-2-0-cust25.3-3.cable.virginm.net. [81.101.201.26]) by mx.google.com with ESMTPSA id fb4sm26840821wib.8.2013.10.27.09.11.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 27 Oct 2013 09:11:38 -0700 (PDT) Message-ID: <526D3B3A.3060505@gmail.com> Date: Sun, 27 Oct 2013 16:11:38 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: PHP internals References: <526D195B.9000204@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine From: rowan.collins@gmail.com (Rowan Collins) On 27/10/2013 15:51, Nikita Popov wrote: > Unless we have *concrete* plans regarding PHP 6 saying "this should go > into (a hypothetical, non-existing) PHP 6" is roughly equivalent to > just declining the feature. I agree with that, and think it is a real problem, but there are two solutions: abandon the BC rules for 5.x releases, or make some concrete plans for 6.x. Otherwise, the release process might as well not distinguish minor and major releases at all, and just define what is and isn't allowed in terms of BC for the foreseeable future of PHP. > PHP 6 only makes sense to me if we're planning to actually do changes > with major BC impact. Not things like this RFC, but changes of basic > language semantics (like fixing the 0 == "foo" comparison and other > foundational issues). Not every major release has to fix everything. An overhaul of error handling, in general, would seem like a good Big Feature to pin a major release on, just as Unicode strings would have been, had it gone ahead. -- Rowan Collins [IMSoP]