Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102464 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24998 invoked from network); 26 Jun 2018 19:28:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jun 2018 19:28:34 -0000 Authentication-Results: pb1.pair.com header.from=spam-free@blueyonder.co.uk; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=spam-free@blueyonder.co.uk; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain blueyonder.co.uk designates 80.0.253.67 as permitted sender) X-PHP-List-Original-Sender: spam-free@blueyonder.co.uk X-Host-Fingerprint: 80.0.253.67 know-smtprelay-omc-3.server.virginmedia.net Received: from [80.0.253.67] ([80.0.253.67:56548] helo=know-smtprelay-omc-3.server.virginmedia.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A4/53-01794-ED3923B5 for ; Tue, 26 Jun 2018 15:28:32 -0400 Received: from [192.168.0.100] ([82.47.50.152]) by cmsmtp with ESMTPA id XtdafkUgabtAcXtdaf9cTb; Tue, 26 Jun 2018 20:28:26 +0100 X-Originating-IP: [82.47.50.152] X-Authenticated-User: spam-free@blueyonder.co.uk X-Spam: 0 X-Authority: v=2.3 cv=QvlwI26d c=1 sm=1 tr=0 a=TAE3a1YMiMiF8Y4yWzocug==:117 a=TAE3a1YMiMiF8Y4yWzocug==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=67BIL_jfAAAA:8 a=2JhU0jsi7qmBFHpwx3kA:9 a=QEXdDO2ut3YA:10 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=blueyonder.co.uk; s=meg.feb2017; t=1530041306; bh=/GajyTdDEOVn3H96DMBSR01rKxQOSF8wkJgsqx2McOM=; h=Subject:To:References:From:Date:In-Reply-To; b=hsVH54rQlCpwID5guo13YdV8LjgyIC4p3n9JSJfVn5GhYEmD4sa/T0xA3nF3JZANE I1TidKp23syyG2BE2SMJhNB+kxhekTmWDCUjpBLt93p4shh/l96j+zxG+PXrA57NYA BfBKMPLSC3erl0nb3r/H15Lf5oI/kImQQU9W0V9AeJ8tCg1begPon02Mg3W/k0SVkB SkAu0VexqURMM7AE/oq5ktUjN7whrfe6QWAd9EwN/8DD9xyWZfv+XiygmFq4YMzYDX k+KIUBNbRf/SJwimSHUIrOeskir1lJLr+GUwwxvznjkI74Rv+1BC07phhNKgG1ahxl /0g2n+JxbfQsw== To: internals@lists.php.net References: Message-ID: <17c367f8-3aeb-277f-36c3-f019e6d0d27a@blueyonder.co.uk> Date: Tue, 26 Jun 2018 20:28:26 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfC16+/u9dMnq3yq4BBaaLo12erctQdv6oD3wFg5sUkJVVjIKg7/7WSlgiLB0GyGvsJ0DXSzr55Yj0uhhv6gDWWMomDG8NTSsJPmP9yTGOYvn1EL/uh/8 F9FmmwCkryiHgWqpNVbNAHfdxlMh8PqqXysvFKPyznQoejvf5/CL9R4/v04QJ+jV5vUPeSvFG4mN1w== Subject: Re: [PHP-DEV] [RFC] Deprecate and remove continue targeting switch From: spam-free@blueyonder.co.uk (niel) On 24/06/18 17:16, Nikita Popov wrote: > Hi internals, > > Another small deprecation for your consideration... > > https://wiki.php.net/rfc/continue_on_switch_deprecation > > Regards, > Nikita > IMO the proposed illustrations will lead to as much, if not more, WTF from other language users as current behaviour. Why? Because the programmer still has to account for the 'switch' in how continue works. This will just cause a BC problem for older code without adding anything for people new to PHP. My suggestion, is to make the break (no pun intended) be clean. Deprecate use of continue from usage to escape switch completely in next PHP, then remove that functionality in PHP 8.