Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98470
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.67 as permitted sender)
Date: Fri, 10 Mar 2017 14:20:28 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CAPhkiZz6dm4ySNJTD_j21DKcGGGDPZnAUFUp_wOt9XBQfFFgzA@mail.gmail.com>
References: <CAPhkiZzs=kLF-JKBjX4bVgADz+nonERWuZYiYo8cXA=GrXKU=g@mail.gmail.com> <f60b8e05-c5d8-0437-37b5-a4b23911fdbb@fleshgrinder.com> <fb25f8bc-2b7c-a27d-6861-039b67c19971@gmail.com> <CAPhkiZzus6-LW8g-fxeBYymEq2FGLOfMS2DKZ16KPOXfaxr+AQ@mail.gmail.com> <24efb0e7-b0e3-68ed-5f42-2d5481f8f291@gmail.com> <CAPhkiZwr0Xff-+NR1OE7cnVD7AoHKRBR43h0S76TfWdrjK6kaA@mail.gmail.com> <44add374-6c4b-399a-c542-8d7f100dfaa3@fleshgrinder.com> <CAPhkiZyFOxDgubcdpxwSXVRVjim-2ALzN9gYs7D6gvf6UXqeAw@mail.gmail.com> <cb81577f-5f0f-b10c-902c-2f17e7fc145b@fleshgrinder.com> <CAPhkiZz6dm4ySNJTD_j21DKcGGGDPZnAUFUp_wOt9XBQfFFgzA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net,Andrey Andreev <narf@devilix.net>
Message-ID: <D231949A-8A25-4BFF-A50B-553A70BE6B1E@gmail.com>
Subject: Re: [PHP-DEV] [Discussion] is_string(), string type and objects implementing __toString()
From: rowan.collins@gmail.com (Rowan Collins)

On 10 March 2017 10:57:42 GMT+00:00, Andrey Andreev <narf@devilix=2Enet> wr=
ote:
>I'm not really interested in making "strict mode" less strict - it's
>already opt-in and non-enforceable=2E
>I want ways to write stonger-type code in "non-strict mode", because
>the fact that "strict mode" is non-enforceable means I can never rely
>on it=2E

This is a common misconception - you can absolutely rely on strict mode en=
forcing your contract=2E

Basically all that happens in non-strict mode is that if the caller writes=
:

foo($value);

The compiler automatically changes that to:

foo((string)$value);

(That's not literally how it's implemented, but it's the effect you get=2E=
)

As the receiver of that parameter, you can't tell, and don't care, if it w=
as the human writing the code who added the cast, or the compiler adding it=
 for them=2E

You can't detect someone blindly writing "(string)" everywhere any more th=
an you can detect whether they are running in strict mode=2E Nor can you kn=
ow if they took it straight from unfiltered user input, or copy-pasted a li=
teral string to 10 different files, or a hundred other things you'd really =
like them not to do=2E All you know is, you asked for a string, and you got=
 one=2E

Regards,

--=20
Rowan Collins
[IMSoP]