Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101850 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68194 invoked from network); 12 Feb 2018 20:35:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Feb 2018 20:35:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=david.proweb@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=david.proweb@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.193 as permitted sender) X-PHP-List-Original-Sender: david.proweb@gmail.com X-Host-Fingerprint: 209.85.223.193 mail-io0-f193.google.com Received: from [209.85.223.193] ([209.85.223.193:46300] helo=mail-io0-f193.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8A/B5-26725-DAAF18A5 for ; Mon, 12 Feb 2018 15:35:58 -0500 Received: by mail-io0-f193.google.com with SMTP id k80so7382983ioe.13 for ; Mon, 12 Feb 2018 12:35:57 -0800 (PST) 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=nF6nvTfIromXp494RPuoo1ohvVBDanyPZS+QWKAF9/8=; b=CQV2GdNjNM2Tc7RKIwVpnmhhIJcPArhsE/mFH/b6Zu3RYyp4MVB3gfEnzqOU1/C1eA QJfH1y9MGCKkSxJUMJU0WlRqDobisrZqpEdetn9GEIRoaTa0UYrWZkv3ta7Q7zWT2Hvz yQjT9jXLOYrbsV2D7GBOdiY+dcUvqU7vm1zDpIMtSLqXOrWAepmfnV5rguWZB57IHUnF FnrYKpW13YHXheU1w5YLj0UVe0YVZ5bEtGAQOi2bJMsBS7D+OJFsBjUbA4Ya3uPVjY9B IYWDmLKQNnTO3QEoQ6UyXd8lkRP3ReK0Ko5BKMiNsDOqpcdtrfWLcskkEOVymJ0RH0Nh 13RA== 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=nF6nvTfIromXp494RPuoo1ohvVBDanyPZS+QWKAF9/8=; b=c0BQrw3Q6Nc97FysyccXzvDIQE5g8dPz4Wj2I7Kknsi6zpLTQo6dWiShPXJfyhc64+ 3KNx6HWXFRiW8PqHEidHx0id6POCV72Mg0vBBx7PB4wZvrTi0N4NVgZL1deWmRRP0fne CcndlSVyyIYTsADt5B4ZsJqSAN1t2R1xeIUx3q7sWGOnX6wKpNxDMGSs/J6a80dsixsG 6TVjppr7O9R4yWa6vPzAqT7Hexj/ZtmtHokj7dIhT5KM2x97ypvyLgB3HSDxdZj8qeSj 6fifMmGqAxUebzqCKLO0QvryBQgy0xNr6BBkYbFzreuP8qBWYwhwLOKvcOYzKNyjfZ5K pB9Q== X-Gm-Message-State: APf1xPDG8y2nc5poWXnJu8IOMzgfS4E/l1OR9GpbjYBIDze6tAi1AeZ6 LaQ68Sv48I/RdNjG41wYWwnpv27IzecttLoXlD8= X-Google-Smtp-Source: AH8x227znEqI8Upu+SXbxjmfBOir1VEI4vfQZ+zoHBABuelbj22+tPxhei+SRoblY/nKZJs1BCERvcppgKCXmRgagUQ= X-Received: by 10.107.14.73 with SMTP id 70mr4300204ioo.258.1518467754962; Mon, 12 Feb 2018 12:35:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.48.211 with HTTP; Mon, 12 Feb 2018 12:35:54 -0800 (PST) Received: by 10.2.48.211 with HTTP; Mon, 12 Feb 2018 12:35:54 -0800 (PST) In-Reply-To: References: Date: Mon, 12 Feb 2018 18:35:54 -0200 Message-ID: To: Wes Cc: Stanislav Malyshev , PHP Internals Content-Type: multipart/alternative; boundary="001a113ff69c23366d056509d34e" Subject: Re: [PHP-DEV][RFC][DISCUSSION] Deprecate the backtick operator From: david.proweb@gmail.com (David Rodrigues) --001a113ff69c23366d056509d34e Content-Type: text/plain; charset="UTF-8" I totally agree to deprecate and remove it in 8.0. Some reasons: It usage is very rare (actually, I don't remeber the last time that I see that in use). Even in old codes. It too could causes confusion with single-quote in some fonts, sizes and styles. Is more easy to identify shell_exec() than backtick usage, anyway. It have exactly the same behaviour than shell_exec(). Do not need adapt usage beyond of the replacement itself. Some keyboard layouts (like mine, ABNT2) requires to press shift+backtick key then space to print a single backtick. Other option is I print two backticks at sametime (is what I do when I work with Markdown). Backtick inside backtick requires a most rare slash backtick to escape it: `\`` (actually, I even know if it works haha) Bonus/curiosity: is hard to find the definition of backtick if you don't know the name of this symbol in english. In portuguese it is called "acento grave" (something like "grave accent"). The remotion of this "feature" will allow use the backtick character to another thing futurely (which could be decided carefully). Or even unused forever. Em 12 de fev de 2018 5:43 PM, "Wes" escreveu: > Again, the reason is: in case in future PHP wants to use backticks for > unicode strings, like javascript. > If the community think it's feasible, in PHP 9, 10, whatever, it must be > deprecated asap. > If you think PHP should use a different syntax for unicode strings in > future, you vote no. > It's as simple as that. I am asking to reserve a particular syntax for > something that could be needed in some years. > --001a113ff69c23366d056509d34e--