Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102581 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3315 invoked from network); 4 Jul 2018 17:16:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jul 2018 17:16:36 -0000 Authentication-Results: pb1.pair.com smtp.mail=nikita.ppv@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=nikita.ppv@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.44 as permitted sender) X-PHP-List-Original-Sender: nikita.ppv@gmail.com X-Host-Fingerprint: 209.85.214.44 mail-it0-f44.google.com Received: from [209.85.214.44] ([209.85.214.44:38192] helo=mail-it0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 24/C5-55607-2F00D3B5 for ; Wed, 04 Jul 2018 13:16:34 -0400 Received: by mail-it0-f44.google.com with SMTP id v83-v6so8879654itc.3 for ; Wed, 04 Jul 2018 10:16:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ku6AuBA61pW+rYbQIIhznjVsxarIZhzWoG1T6FGBo4c=; b=GgcN5g6UvsBXQUKgX3DxLO46cTrqHTpAeG6Myl1jKd4Eb/lqMZhUrESQ33ctAuUjAp Uf9bDo81M6WhtwJcLdLyojgfMQfpvKn8xDPR2qekdlw2RyJnBh3Vbp/g0NUCox9RwPQa CMbWJddtMlxNgCKWaapInvHpo5i9M7GJEbG+89ckjod5r1NvPS0a3gewcc0FnuZRFnjv sIy7PmhPlMsSGHd/2LFc/sTvpvHnKD+2XhJI+nRXlG0hm+A8ioAPlepCon7kBi9YUC6d lUYtFy1BbTYn5NbJG/qzEZ0+/cefmXajhAL3QK0Wpsaarwh1zxp498D+ihnu9qByFXWU dWNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ku6AuBA61pW+rYbQIIhznjVsxarIZhzWoG1T6FGBo4c=; b=NHiRdOzHMhyYVu50rAlBAZuoJlJJPBtXm4FZTYmjYokmBY58bJCZaFXuyQ3z0BObAq BMpUUvlCcQ133wXwuMBaXCE1joN4OAJBD3Mkax+DIOiD5lo4pkP3UxqnN5tH2cD7Ja6k q2asCej7PJxU2aAdKXcSBITTY0LrBMLjz0rSAA+3V+3/JhhzI7+B4U1LnWzwCqOf5xyV WJyV3zuKJUcoFxMddSMAHy1I4km2nCxyP+JXXEapso/wyJ4DV4NLYMyRcFjbJbLfjeek O1I6cysKw+ErWXMfq4k2F3GGgUkuS3aajnt2olgSO+eYNUXoXg2u2esMo8PDfQyZQNNk ZPyw== X-Gm-Message-State: APt69E2I+n8suV8juQhw+IFZY+sIpQ/5W095axP0/h0N+SLtJpvDlTQG CW/GsPRi/Bj79F2orNUeiWiDKRnOlD6+jK/CCnQ= X-Google-Smtp-Source: AAOMgpf7wlkoDdoK0OEelyyzptTJeMuwDTt+wD4TfFYaIaBtpX+HqPQiEdh74GvPQfX22U2q+ZFJgsxSlIJs7ASum6E= X-Received: by 2002:a02:503:: with SMTP id e3-v6mr2358384jad.29.1530724591352; Wed, 04 Jul 2018 10:16:31 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a6b:148a:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 10:16:30 -0700 (PDT) In-Reply-To: References: <17c367f8-3aeb-277f-36c3-f019e6d0d27a@blueyonder.co.uk> <94ff9afc-b3b0-0ae2-55bd-ce6c3936967d@gmail.com> Date: Wed, 4 Jul 2018 19:16:30 +0200 Message-ID: To: "Christoph M. Becker" Cc: Zeev Suraski , Stanislav Malyshev , Rowan Collins , Internals Content-Type: multipart/alternative; boundary="0000000000008441e905702f972a" Subject: Re: [PHP-DEV] [RFC] Deprecate and remove continue targeting switch From: nikita.ppv@gmail.com (Nikita Popov) --0000000000008441e905702f972a Content-Type: text/plain; charset="UTF-8" On Wed, Jul 4, 2018 at 5:28 PM, Christoph M. Becker wrote: > On 04.07.2018 at 16:51, Zeev Suraski wrote: > > > On Wed, Jul 4, 2018 at 5:15 PM Nikita Popov > wrote: > > > >> On Wed, Jun 27, 2018 at 11:07 PM, Stanislav Malyshev < > smalyshev@gmail.com> > >> wrote: > >> > >>>> In the proposal, the code is valid in all versions of PHP up to and > >>>> including 7.3, *and represents the same algorithm in all versions*. > The > >>>> only difference would be the side-effect of issuing an additional > >>>> deprecation notice; that's not "a different meaning". In PHP 8, under > >>>> Nikita's proposal, the code would not be valid at all. > >>> > >>> I agree with PHP 7 part but not with PHP 8 part. I think we should just > >>> leave the warning there. > >> > >> I don't care particularly strongly about the actual removal, just > having a > >> warning would serve the purpose just as well for me. > >> > >> Should I just go ahead and implement the warning (with no intent of > future > >> removal), or do we want to still go through the RFC here? > > > > I think a sensible warning is fine and doesn't really require an RFC... > > Would be fine for me as well. > Okay, thanks for the feedback. I've implemented the warning in https://github.com/php/php-src/pull/3364 and will merge the PR in a few days if there are no further objections. Nikita --0000000000008441e905702f972a--