Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107779
To: Claude Pache <claude.pache@gmail.com>,
 Theodore Brown <theodorejb@outlook.com>
Cc: Reinis Rozitis <r@roze.lv>, PHP Internals <internals@lists.php.net>
References: <5d976928.1c69fb81.db3a8.78daSMTPIN_ADDED_MISSING@mx.google.com>
 <CAF+90c9uXdqJsTizLCca-AswenZDv9-6yw=ranATp3XoutHyxw@mail.gmail.com>
 <DM5PR06MB285747B847DE2D7320758C05DE9A0@DM5PR06MB2857.namprd06.prod.outlook.com>
 <e69fb3de-df5f-f77e-ad4e-61ea30185c5c@lsces.uk>
 <CAG9XoMR9DhKDwS1moH_9pjDNyZQ70ER5_stNs_GxQFucZ+ar7A@mail.gmail.com>
 <000601d57dc7$ddb9e890$992db9b0$@roze.lv>
 <SN6PR06MB3855F9A8CFF8CF060796C4F8DE9A0@SN6PR06MB3855.namprd06.prod.outlook.com>
 <CA1DFCBE-2ECF-46D7-8F35-E8BDD97DEEDF@gmail.com>
Message-ID: <18b8e210-8f82-67c1-3fd5-9f651dc7c086@telia.com>
Date: Thu, 7 Nov 2019 11:26:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CA1DFCBE-2ECF-46D7-8F35-E8BDD97DEEDF@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] Deprecate Backtick Operator (V2)
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)


Den 2019-10-31 kl. 16:48, skrev Claude Pache:
>> Le 31 oct. 2019 à 15:59, Theodore Brown <theodorejb@outlook.com> a écrit :
>>
>> 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.
>>
> 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.
>
> Sorry for the rant. But the message is: Existence of precedent is not an argument, because it may be a bad precedent.
>
> —Claude

Hi,

I think that RFC was an example where there was a clear cut case
for removing curly brace array access, but not equally clear on to
remove it for curly brace string access.

In my eyes that RFC would have benefited from having two votes,
but the baby went out with the bathwater so to speak.

r//Björn L