Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104759
MIME-Version: 1.0
References: <OF2EDD3BDE.BAC08076-ON432583BE.004A746C-432583BE.004B009B@alfabank.ru>
 <CAF+90c8Xn7yZEkER_dPq9Dv6w_p1dsg6DtF7goo6+4Tb5GwG_Q@mail.gmail.com>
 <CAJW__o3w8sdxbrjF7PFDAXP2b31-LMad0_1BQGfvcgFvRqEh9g@mail.gmail.com> <CAFMT4NqNQuM2Xdfap=kVakF9aLJpv+eK1==iE+gKHiTV1bKcPA@mail.gmail.com>
In-Reply-To: <CAFMT4NqNQuM2Xdfap=kVakF9aLJpv+eK1==iE+gKHiTV1bKcPA@mail.gmail.com>
Date: Fri, 15 Mar 2019 18:08:22 +0000
Message-ID: <CALKiJKqRYdpbufrRn03b8O4_xKniYAmv_ZwevnCdfnxrs22XCA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000051da78058425ed99"
Subject: Re: [PHP-DEV] Proposal for deprecate alternate syntax(curly braces)
 for array and string access
From: rowan.collins@gmail.com (Rowan Collins)

--00000000000051da78058425ed99
Content-Type: text/plain; charset="UTF-8"

On Fri, 15 Mar 2019 at 17:53, Levi Morrison <levim@php.net> wrote:

>   1. I cannot think of *any* reason to separate them. If you want to
> make sure you are indexing a string, *do a type check*, not bake `{}`
> into only working on strings.
>


I think it's more common to do the opposite: think you're working on an
array, and accidentally pick up a string.

If we separated the syntaxes, it would be possible to always raise a
warning when that happens, rather than silently returning the Nth character.

To be honest I can't remember the last time I used *either* syntax for
string access, other than by accident.

Regards,
-- 
Rowan Collins
[IMSoP]

--00000000000051da78058425ed99--