Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106953
MIME-Version: 1.0
References: <CAF+90c9Kc6m_bv=aJxbD3-RmnNXXLqv6mPjHp7U7qxX_ck27qw@mail.gmail.com>
 <CAF+90c_KHYm1SLOKkZXM6xurYiDTX3=hbijpD8rT1OSUHSod_w@mail.gmail.com>
 <CEC35EF9-9956-44BE-8C8E-EE5FC3D5A7C7@gmail.com> <D5DDA318-E953-4AB8-873F-7CA7264722E2@koalephant.com>
 <E30D9A22-9842-4A67-ABA5-A339875FFE12@gmail.com> <CAG9XoMTG3OLbD0BfWv+ORUUsbMV2CaF0Ea4NLF1huHBr5JCmWQ@mail.gmail.com>
 <CALKiJKrftDt1ohJQLrgx+n57nf-TMVpUKYRVKWBkCa-ND1LVMg@mail.gmail.com>
 <CADyq6s+C07KABQcZ9x+vgH8pYdVcGZcx6m8Dg+E+LYn1RgOLoA@mail.gmail.com>
 <DED63BF6-96C5-475B-A263-C2E71961D8A6@gmail.com> <CAPKYkKz2TOLR1dzRMDZZHd_S5mVkOxoX2_+19+bG2zs_FYcMLQ@mail.gmail.com>
 <CAL0xaBE7oJphP2zfojHywv9znVBfT4-35HSCJB7esO511tBirQ@mail.gmail.com>
In-Reply-To: <CAL0xaBE7oJphP2zfojHywv9znVBfT4-35HSCJB7esO511tBirQ@mail.gmail.com>
Date: Thu, 12 Sep 2019 10:11:13 -0400
Message-ID: <CAPKYkKx11SGP+8xgA1RWp3n1e7NwYL+J6adsdCZC20VqzeaBAA@mail.gmail.com>
To: Arvids Godjuks <arvids.godjuks@gmail.com>
Cc: Claude Pache <claude.pache@gmail.com>, Marco Pivetta <ocramius@gmail.com>, 
	Rowan Tommins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000076956605925bb6d7"
Subject: Re: [PHP-DEV] [RFC] Reclassifying engine warnings
From: chasepeeler@gmail.com (Chase Peeler)

--00000000000076956605925bb6d7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 12, 2019 at 10:06 AM Arvids Godjuks <arvids.godjuks@gmail.com>
wrote:

>
>
> =D1=87=D1=82, 12 =D1=81=D0=B5=D0=BD=D1=82. 2019 =D0=B3. =D0=B2 16:02, Cha=
se Peeler <chasepeeler@gmail.com>:
>
>> On Thu, Sep 12, 2019 at 9:55 AM Claude Pache <claude.pache@gmail.com>
>> wrote:
>>
>> >
>> >
>> > > Le 12 sept. 2019 =C3=A0 15:33, Marco Pivetta <ocramius@gmail.com> a =
=C3=A9crit
>> :
>> > >
>> > > $foo[$key1][$key2] =3D ($foo[$key1][$key2] ?? 0) + 1;
>> > >
>> > > Marco Pivetta
>> >
>> > That violates blatantly DRY (twice the exact same lengthy expression
>> > `$foo[$key1][$key2]`), so it is not a satisfactory solution.
>> >
>> > And that's why PHP is so awesome. You don't have to do all these stupi=
d
>> tricks just to do something simple like increment a counter. But, it loo=
ks
>> like we're going to throw that out of the window because some people thi=
nk
>> that since they like doing it like the way above, everyone should have t=
o.
>>
>> > =E2=80=94Claude
>> >
>> >
>>
>> --
>> Chase Peeler
>> chasepeeler@gmail.com
>>
>
> Easy, because experience shows that leads to bugs and lots of them.
> Security issues even.
> If you want to write predictable code - you have to init your
> variables/arrays. And check for existence/null. If fixed at least a few
> dozen bugs in my system I took over in the last few months specifically
> because of undefined variables or indexes.
>
> Never once have I advocated not initializing variables or arrays. I'm jus=
t
saying that we shouldn't force such behavior. Many of us can figure out
when we need the extra boilerplate and when we don't. Don't force us to
have to deal with the additional burden in every single case because
someone else can't.


> It works for small stuff, but when you have a codebase with 100+k LOC and
> more, you have to go strict or it starts to cost a lot of money and
> personnel to keep things running along.
>
> --
> Arv=C4=ABds Godjuks
>
> +371 26 851 664
> arvids.godjuks@gmail.com
> Skype: psihius
> Telegram: @psihius https://t.me/psihius
>


--=20
Chase Peeler
chasepeeler@gmail.com

--00000000000076956605925bb6d7--