Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107436 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 2850 invoked from network); 8 Oct 2019 22:47:25 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 8 Oct 2019 22:47:25 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 120922D19B3 for ; Tue, 8 Oct 2019 13:29:54 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Tue, 8 Oct 2019 13:29:53 -0700 (PDT) Received: by mail-io1-xd2c.google.com with SMTP id q10so39575816iop.2 for ; Tue, 08 Oct 2019 13:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tq/H+kpsI44cEOweE5eZYaaiFZZXMP3SNWoanmi9M/M=; b=oOj3vxhnJDUxYhE60e7+9ZhphYrg5JOo0g/HL43revKGMOfghqlXJVVdpFUAXPsMPA oSBK0dkNnZLAO678Vg8zjZb1f2P9AnEzu6U0nRREMKFExSbtwlVdgOgVYoIyeu8/WZ0o 94r1N02J/zMjl6K0+re/TLSOxa1pSK80ofdmbJK9yDHPgjb59W5fKZA6Onev2Qyhypx2 237/Tb1OuP+lMMrLXHQwEjC/y1IU6BWFsD+jk8ZeNAPJk4EVh5y/GKEwx6P5uKeD+Sz9 1xkFGSvWBeElmGyYlINEio71lbESSSfu7UrWpnb5k8wQqoeJuL3+EgNtRCIvtyfNEwGj Yk2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tq/H+kpsI44cEOweE5eZYaaiFZZXMP3SNWoanmi9M/M=; b=p7pEK/PCeBm3O86jR9NlEuWo7oC/PmjBRsLwbvFaBvfx1RWXzvcAPbEHzLV/skD93T RaKkbsz0sxvLN5TM/xvs3YT0LLKglUNb121CPVSE0qViLxSCRSLzL4bYpuDyz6DkvN/j vvmnStoJNX8UZeNJc6+hHx4EpML5wth+PA16sVSep0sqnUHNvhLXMkyMC4xqW5FH6pT3 ey3Mnj5P9W6PnvRZQM7Lz2ran5bVoQnOufU6gwlcDydiUyyT2YOPLxjA1ukch5t/YHrT T0TlVmnrE3quLkZUMCk0AfUSHeTn4AEXOC/yfbs80432yXYqmzex/dmfg3L5t0r+QtTO tSHA== X-Gm-Message-State: APjAAAVurCTENhxASmqncJSzUo95Xzm+m/ml80JqHMsCtU3ggmz/TxUN +Cr6MLx/7ZnUGTVVdQaffoMzQ5thUPvvlnFEMbA= X-Google-Smtp-Source: APXvYqzAOxoPBnxxj/Jhqf9Aj2QzTX2wUCvW8Zb2mjQjC9ygqYQteFh4Gf3N6DUL92dK4bScoc3wMMGvlfYyjxRHEl4= X-Received: by 2002:a02:cd06:: with SMTP id g6mr32750735jaq.89.1570566592863; Tue, 08 Oct 2019 13:29:52 -0700 (PDT) MIME-Version: 1.0 References: <5d976928.1c69fb81.db3a8.78daSMTPIN_ADDED_MISSING@mx.google.com> <413d377a-4ce1-a521-0cb4-5bb37e84c257@gmail.com> <6DFA91F7-0005-453E-A314-A5DFE1A4D3D3@newclarity.net> In-Reply-To: <6DFA91F7-0005-453E-A314-A5DFE1A4D3D3@newclarity.net> Date: Tue, 8 Oct 2019 22:29:27 +0200 Message-ID: To: Mike Schinkel Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000dd22fc05946c077b" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Deprecate Backtick Operator (V2) From: kjarli@gmail.com (Lynn) --000000000000dd22fc05946c077b Content-Type: text/plain; charset="UTF-8" On Tue, Oct 8, 2019 at 10:12 PM Mike Schinkel wrote: > My, my this is a heated topic. > > I am commenting in part because I do not have a dog in this hunt. I am > okay leaving it, I am okay if it is deprecated. There are other things for > PHP that I care far more about than this RFC. So... > > I am wondering if everyone participating in this discussion would be > willing to ask themselves "Is there any middle ground where I can respond > in a way that is win-win for everyone involved?" rather than retreating to > each other's respective corners and fighting as if to the death? > Hi, My middle ground is a vote, regardless of outcome. This RFC is pretty simple, a deprecation + removal in a later patch, there's not much to compromise on the implementation. If people think a deprecation should not be done or if it's not worth it, a vote is the way to show that opinion. Pros and cons have been given and people have different opinions about those. Currently a few people on the mailing list are very vocal up to a point where it becomes obnoxious to read their replies, and others are stating that this RFC shouldn't even go into a vote. If there are enough reasons to not deprecate them, the voting process will show this and the RFC will be rejected. Regards, Lynn van der Berg PS. We need a CoC. --000000000000dd22fc05946c077b--