Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84381
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.179 as permitted sender)
MIME-Version: 1.0
References: <075201d04f82$abd721d0$03856570$@php.net> <54F8D69B.6000704@pascal-martin.fr>
Date: Fri, 06 Mar 2015 14:36:43 +0000
Message-ID: <CACwt+JfV5bTi4DjfttJV=A9uLGRBtvqSzWv6NgTQaUoLY-gqeA@mail.gmail.com>
To: "Pascal Martin, AFUP" <mailing@pascal-martin.fr>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d04428ace0f32f205109f9df0
Subject: Re: [PHP-DEV] [RFC][VOTE] Improve array to string conversion
From: patrickallaert@php.net (Patrick ALLAERT)

--f46d04428ace0f32f205109f9df0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Le jeu. 5 mars 2015 =C3=A0 23:20, Pascal Martin, AFUP <mailing@pascal-marti=
n.fr>
a =C3=A9crit :

> Le 23/02/2015 17:06, Fran=C3=A7ois Laupretre a =C3=A9crit :
> > Starting the vote for https://wiki.php.net/rfc/array-to-string.
>
> Hi,
>
> We talked about this with other people at AFUP and a great majority of
> us agrees that the current behavior of array to strings conversions is
> not quite useful


Nor are all the following operations:

$useOfUnexistingVariableIsOkToContinueExecution =3D $variableNotSet;

$obj =3D new stdClass();
$useOfUnexistingPropertyIsOkToContinueExecution =3D $obj->notFound;

$computingWithObjectIsOkToContinueExecution =3D 42 + new stdClass();

$array =3D array(42);
$useOfUnexistingOffsetIsOkToContinueExecution =3D $array[42];

$int =3D 42;
$usingANumberAsAnArrayIsFineNoNotice =3D $int["foo"];

$null =3D NULL;
$usingANonObjectAsAnObjectIsOkToContinueExecution =3D $null->notAnObject;

$resource =3D fopen("/etc/hosts", "r");
$resourceToStringConversionIsOkToContinueExecution =3D (string) $resource;

Running the above would produce:

PHP Notice:  Undefined variable: variableNotSet in - on line 2

Notice: Undefined variable: variableNotSet in - on line 2
PHP Notice:  Undefined property: stdClass::$notFound in - on line 5

Notice: Undefined property: stdClass::$notFound in - on line 5
PHP Notice:  Object of class stdClass could not be converted to int in - on
line 7

Notice: Object of class stdClass could not be converted to int in - on line
7
PHP Notice:  Undefined offset: 42 in - on line 10

Notice: Undefined offset: 42 in - on line 10
PHP Notice:  Trying to get property of non-object in - on line 16

Notice: Trying to get property of non-object in - on line 16

-- and, for several of us, when we started getting
> notices with PHP 5.4, it actually showed us there were bugs in our
> applications.
>

Which confirms that turning notices 'On' would allow anyone to fix code
that may seems suspect.


> So, we are +1 on this.
>
> Basically, even if notices are already bringing some useful information,
> we feel being more "strict" and "explicit" than that might help, here.
>

Why suddenly changing that specific notice, without deprecation, to one
that stop the execution and without "opt-in" for it? (and according to the
patch, only in some "array to string conversion", not all?)

I'm about to post another suggestion in a fork of this discussion which
might fit anyone, stay tuned!

Cheers,
Patrick

--f46d04428ace0f32f205109f9df0--