Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101841 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39851 invoked from network); 12 Feb 2018 14:38:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Feb 2018 14:38:42 -0000 Authentication-Results: pb1.pair.com header.from=eli@eliw.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=eli@eliw.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain eliw.com designates 209.85.216.170 as permitted sender) X-PHP-List-Original-Sender: eli@eliw.com X-Host-Fingerprint: 209.85.216.170 mail-qt0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:36678] helo=mail-qt0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/A1-26725-1F6A18A5 for ; Mon, 12 Feb 2018 09:38:42 -0500 Received: by mail-qt0-f170.google.com with SMTP id q18so12369194qtl.3 for ; Mon, 12 Feb 2018 06:38:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eliw-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Hmr0qLUigJbm8T+CLN0olnOMZcgnInSZLGaJop9ODhA=; b=scWY56YWBjm7ZGifY148CUv3+3jAqat0zmOi/bDVi7IHN+QQIopwGl22RNg8ShxcH5 zkL9c/47D+4KOaHwDcgDmf49Ui0GoZxpSLgVtHKIIwjYJnwTI7G0L/M5eBqs6uRqx4PL al8wqy2hpyoA3r86teYjtYDOfAhBLD3uWIrDhE2GTrzaTBoXvYQrq5ihYMNpU1S9sPhE sSFuuqmGBFFL16rD8l+fejRPFaZ7ya3OkdR+Zy0Jf1z6UmpeapA70lwWMbYEJeBNM/w4 WVQNkRJ5vseIg1LKF+3bL25GT5ROvfJwbXbH2AWgS0EOzOPsy/VFVBciuLIFCLV2hibU xA5w== 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=Hmr0qLUigJbm8T+CLN0olnOMZcgnInSZLGaJop9ODhA=; b=FSt/i7wAeII2eoYfFiSvDwrdOuuNk5LZIsnDFSo5ODLVdjqpLQf5D+ll7dlzpb6ekh ktQC7sIi5HkZcLaaKHup3iFE+kA/hVZtK2V15BQFRWNpK6TCBCgID2/ClA8GYo4PeyXl ABGJSanu5L09QjoMwGRiFT3Csw6/iXgE5r3+9dycA6rSN80jIj2tC6WzOd2Gvz2DEH7I hGFMI7hyLKM1ktNzDizW3evXhgHK1rVupmhOyvLMO84Q9rvD9BzR3ZSaQql9B3tSyIc9 DJKt13qfo5WAAO/J+7w4SiUCJiwsiQrTdIthVpOC+/umm2kXmezfrgxHxNFUIexUU5hM cOJQ== X-Gm-Message-State: APf1xPB8i7NhKav22t1ZSIbs6qZDTbFdJNnGK1JBk/8J9IDTLRCN6QbH DI4RkmEbCjviZqrgesz9OrzF77twm+E0zMPPc33CJg== X-Google-Smtp-Source: AH8x224mR/yNkxga3VM7kgZzmKgVkvvw46fsdUI+mMVlJWvz5aUuxiGLMrHLLkmnG/4A3+hNe0uHW1aQHrXXxnR2Qew= X-Received: by 10.237.47.195 with SMTP id m61mr18534829qtd.32.1518446319122; Mon, 12 Feb 2018 06:38:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.108.75 with HTTP; Mon, 12 Feb 2018 06:38:38 -0800 (PST) X-Originating-IP: [69.243.54.140] In-Reply-To: References: Date: Mon, 12 Feb 2018 09:38:38 -0500 Message-ID: To: CHU Zhaowei Cc: Andrey Andreev , Wes , PHP Internals Content-Type: multipart/alternative; boundary="94eb2c124be87650ab056504d55c" Subject: Re: [PHP-DEV][RFC][DISCUSSION] Deprecate the backtick operator From: eli@eliw.com (Eli White) --94eb2c124be87650ab056504d55c Content-Type: text/plain; charset="UTF-8" I'll chime in on the "What evidence do you have that this is not widely-used" ... in fact, I have seen through my PHP career this used very regularly, and training/workshop/class sessions at conferences still regularly teach this as the 'standard way' to handle shell commands. So I think that this would have a huge impact on existing code, and I am similarly a huge -1. Is it funky that random backticks cause a shell action to happen? Yes. But there are a million funky things about PHP, and we strive for backward compatibility when at all possible. And there is no direct gain/need to remove this feature. Eli On Mon, Feb 12, 2018 at 8:16 AM, CHU Zhaowei wrote: > Hello, > > >But that being said, I do support the proposal. I understand people > >opposed to removing features for no reason, but nobody needs this to > >be an operator, it's not a widely-used one, and we all know if it was > >proposed for addition today it would have 0 chance of acceptance. > > > > How do you conclude that this is not a widely-used one? > > > > btw, you already hit the most important point. Why do we deprecate or > remove feature for no good? > > > > > in case PHP decided in future to use backtick enclosed strings for > Unicode strings > > > AFAIK, since PHP7, we have no plan for unicode string. > > > > Best regards, > CHU Zhaowei --94eb2c124be87650ab056504d55c--