Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106949
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>
In-Reply-To: <CADyq6s+C07KABQcZ9x+vgH8pYdVcGZcx6m8Dg+E+LYn1RgOLoA@mail.gmail.com>
Date: Thu, 12 Sep 2019 16:02:03 +0200
Message-ID: <CAL0xaBHHv0xt=-Fxb9ku945eDFZ_6BXWhmFoqiZhqKzr903m-g@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: Rowan Tommins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a36df405925b96b3"
Subject: Re: [PHP-DEV] [RFC] Reclassifying engine warnings
From: arvids.godjuks@gmail.com (Arvids Godjuks)

--000000000000a36df405925b96b3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

=D1=87=D1=82, 12 =D1=81=D0=B5=D0=BD=D1=82. 2019 =D0=B3. =D0=B2 15:33, Marco=
 Pivetta <ocramius@gmail.com>:

> Hey Rowan,
> <http://ocramius.github.com/>
>
>
> On Thu, Sep 12, 2019 at 3:30 PM Rowan Tommins <rowan.collins@gmail.com>
> wrote:
>
> > For instance, for undefined array keys, what if we had an operator for
> > "initialise and retrieve", such as $foo[? 'bar']. Then we could simplif=
y
> > ugly code like this:
> >
> > if ( ! isset($foo[$key1]) {
> >    $foo[$key1] =3D [];
> > }
> > if ( ! isset($foo[$key1][$key2]) {
> >    $foo[$key1][$key2] =3D 0;
> > }
> > $foo[$key1][$key2]++;
> >
> >
> > With something safe but succinct like this:
> >
> > $foo[? $key1][? $key2]++;
> >
>
> $foo[$key1][$key2] =3D ($foo[$key1][$key2] ?? 0) + 1;
>
> Marco Pivetta
>
> http://twitter.com/Ocramius
>
> http://ocramius.github.com/
>

This message contains a healthy dose of sarcasm.

Hi Marko and Rowan :)

*Me reviewing the PR with that code*
*Clicks "Changes required"
[ Please rewrite this statement into easy readable format with an if ]
* Clicks send *

Think what you must, but 6 months when you come back to code like this you
have to stop, look at it hard and figure out what the hell actually happens
there.
Breaks reading flow.

One thing I like PHP for is a distinct lack of huge amounts of syntax
sugar.
Take Ruby - it's a hell to read the code. Even Vagrantfile has tons of
results about what syntax for arrays to use and things breaking because you
end up mixing stuff and you get at least 4 different answers to the same
question and it looks like all are correct. Confusing as hell :)

What I'm trying to say is some of us choose PHP for it's "there is one
syntax - use it". If people want syntax sugar - there are other languages
that fit that much better. Leave us, peasants, in our peasant non-syntax
sugar world alone :D

But many of us would also like the language engine to tighten up some of
its extremely relaxed parts that do not fit in modern development
environments and the lowest bar of the code quality rise a bit. Otherwise,
the gap between high-end development and newbies is going to be even bigger
than it is now.
I hire people, that's part of my job. One of the criteria is the approach
to errors/warning/notices. Imagine how that goes.

--=20
Arv=C4=ABds Godjuks

+371 26 851 664
arvids.godjuks@gmail.com
Skype: psihius
Telegram: @psihius https://t.me/psihius

--000000000000a36df405925b96b3--