Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107034
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>
 <CAL0xaBHHv0xt=-Fxb9ku945eDFZ_6BXWhmFoqiZhqKzr903m-g@mail.gmail.com>
 <CADyq6sK5UCcLW16osiXshTgz0XUqNFZ9dOnf1pG2FCXJJerROQ@mail.gmail.com> <CAH0Uv3HM0d5odu4Fft=RpJuyhiCKPR2XODYZb6EzW-6-0UtW1w@mail.gmail.com>
In-Reply-To: <CAH0Uv3HM0d5odu4Fft=RpJuyhiCKPR2XODYZb6EzW-6-0UtW1w@mail.gmail.com>
Date: Fri, 13 Sep 2019 01:29:29 +0200
Message-ID: <CANZOY=A+HAomc1ydfnWTgeu6gzc8EwsMc6Tg05JjGZhxo4_tCg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c8129005926382ce"
Subject: Re: [PHP-DEV] [RFC] Reclassifying engine warnings
From: arnold.adaniels.nl@gmail.com (Arnold Daniels)

--000000000000c8129005926382ce
Content-Type: text/plain; charset="UTF-8"

l want to point out that way in which notices and warnings are triggered
when concerning operators, is also inconsistent.
Sometimes a check is done by the function of the operator (or a deeper
function). Other times the operator will simply cast the operand and the
casting produces a notice, warning or error.

As an example; The concatenation operator will implicitly cast anything to
a string. Explicitly casting it has no effect

    [ ] . 'abc'; // Notice:  Array to string conversion
    (string)[ ] . 'abc'; // Notice:  Array to string conversion

But arithmetic operators will do a check. Explicitly casting will remove
any warning or error

    [ ] * 10; // Fatal error:  Unsupported operand types
    (int)[ ] * 10; // 0
    "22 bikes" * 10; // Notice:  A non well formed numeric value encountered
    (int)"22 bikes" * 10; // 220

To some extent, the inconsistent error levels come from a different
approach. Even more, there is a big difference between types that can are
cast silently to a non-sensical value and types where any type of warning
or error is given, for seemingly no apparent reason.

Changing the warning levels without addressing this issue doesn't make a
whole lot of sense.

- Arnold
In the past I suggested operators like
??++
??+=
for this purpose.

But the [? $key] is even better, because it makes it explicit which array
keys we expect to already exist and which we don't.

$var[$k0][? $k1][? $k2]++;

This is great but the second "?" is redundant isn't it?
Tekst uit oorspronkelijke berichten weergeven

--000000000000c8129005926382ce--