Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107744 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 60039 invoked from network); 31 Oct 2019 18:00:12 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 31 Oct 2019 18:00:12 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 77BC02D2006 for ; Thu, 31 Oct 2019 08:48:23 -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: X-Spam-Virus: No Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 ; Thu, 31 Oct 2019 08:48:22 -0700 (PDT) Received: by mail-wm1-x335.google.com with SMTP id x5so6411836wmi.0 for ; Thu, 31 Oct 2019 08:48:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=LiIJ0airjs+h1a5s2mjDfCfNyXKC+rlXC7Ub+SWscOE=; b=MAxYxeee2/zQz7wy2lzzP6aNv3Wl/1/9kkpVhiLuxzVuY/aOUD66j5qzPdWPCcHmzg BK9eSJdZ/ffjwCvaTCb4w4VPJ2yOpRRkZngKAx3kS1OSqcz5s2s6GVpO7v7+vbz9VzXd iOCHevVoA+H3KtTf9KhPPMgmJP4/qMEFhYB2Y8c0P8S5TNqQ6bIeFSHIzH8/yDJwp/B7 hv1faP+ULUH4hpVqmgMCafWbz5FKEuJkcl/jT4FGWepxK/+Zqf6K728Om+sgGWasTXhm 2PTww9IiwThQVD6n+6R+T1zMouOU/nunnIMI2uluCHLrVQyk7Vd6I0ojGGTkiGF6H3nw Ch8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=LiIJ0airjs+h1a5s2mjDfCfNyXKC+rlXC7Ub+SWscOE=; b=OwGwgab4DFR/q4RzRGE5qRzKGlNqO3uf957haXNj3f3zqw+YSFB2MBxvdpdwacij1p JiX0S6dTEICJZB39SKfDs3ouW6SNdKDI9Q8KmMFTS8APw7X/eLGWOfv1oKSmfvKhYQ77 8B6UheDnh/FqDCRCsWJz/TNO+zI/VeXKN+OD570JKefq16i9pl3txhas7y9N1eiL8+mJ yQcnKOceFqrB76EndukQuMLzOWiKw63hMJIYmjzIWfpY5x5xUOT5iDpm7nZpJp/jymcY g83a/3ZsCA7qht49ad1LVJOCoqbliN1sSTua+gc91cqJWDBCPXcW43A7GP35OYZ/C4pM mS5g== X-Gm-Message-State: APjAAAXd5CsIm6ez4lA+jjlHC5en7RKGOLmsxSPJGXiToH80jamkPM03 7i2v1868WbrG5jW6auZcWzc= X-Google-Smtp-Source: APXvYqwC2L8FJOF0MgJs5dEFvM/Ro/iFEFJX52+Ddcbqvqj+JVlVLuv44tyZbTG+YK+w/LArZS4CoQ== X-Received: by 2002:a1c:6146:: with SMTP id v67mr5972659wmb.102.1572536901660; Thu, 31 Oct 2019 08:48:21 -0700 (PDT) Received: from [192.168.0.63] (84-75-30-51.dclient.hispeed.ch. [84.75.30.51]) by smtp.gmail.com with ESMTPSA id s26sm4193970wmh.23.2019.10.31.08.48.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Oct 2019 08:48:20 -0700 (PDT) Message-ID: Content-Type: multipart/alternative; boundary="Apple-Mail=_57FF261C-0339-4615-839F-5D10248C1990" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Thu, 31 Oct 2019 16:48:19 +0100 In-Reply-To: Cc: Reinis Rozitis , PHP Internals To: Theodore Brown References: <5d976928.1c69fb81.db3a8.78daSMTPIN_ADDED_MISSING@mx.google.com> <000601d57dc7$ddb9e890$992db9b0$@roze.lv> X-Mailer: Apple Mail (2.3445.104.11) X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Deprecate Backtick Operator (V2) From: claude.pache@gmail.com (Claude Pache) --Apple-Mail=_57FF261C-0339-4615-839F-5D10248C1990 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Le 31 oct. 2019 =C3=A0 15:59, Theodore Brown = a =C3=A9crit : >=20 > Of course there will always be an infinite number of logical ways to > structure a program, but this is quite different from having two > different syntaxes in a language that do exactly the same thing. The > latter is confusing since it's no longer clear which syntax should be > used. The same situation existed with the curly brace array/string > access syntax, which was deprecated in PHP 7.4. >=20 Yeah, curly brace string access syntax were deprecated in PHP 7.4, and = it was IMO an error. Last day, I reviewed an old library (PHPMarkdown), = whose algorithm (probably directly ported from the original markdown = written in Perl) was not very readable. Replacing all $string{$index} = instances with $string[$index] made it even less readable, because the = conventional distinction between string indexes and array indexes used = in that library (and in several others libraries) were lost.=20 Sorry for the rant. But the message is: Existence of precedent is not an = argument, because it may be a bad precedent. =E2=80=94Claude= --Apple-Mail=_57FF261C-0339-4615-839F-5D10248C1990--