Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82112
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54D6DD7E.5060602@lerdorf.com>
References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me>
	<CAB6YZuy-FFERAqcOjtyiizzwUZb6qrnMw8FCf8zur1wsL37Opg@mail.gmail.com>
	<9E1C2427-0295-4F3E-BD29-04DA84321067@ajf.me>
	<A3ACFAAF-37CB-47ED-9605-BA7D0609E4DA@ajf.me>
	<CAB6YZuzW9zwV7F44_8BxcrcteFMW2c3GJq1bkUuZTC9-tcmtNQ@mail.gmail.com>
	<54D6CC39.50708@lerdorf.com>
	<93AAEA55-1C03-46AD-88D0-6A2F5531FCA6@ajf.me>
	<54D6DD7E.5060602@lerdorf.com>
Date: Sun, 8 Feb 2015 11:33:03 +0700
Message-ID: <CAEZPtU7uouTpLt+FXkVyxn3YK9Tnnbzh6wyTjtnTAJWtAP70LA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: PHP internals <internals@lists.php.net>, Andrea Faulds <ajf@ajf.me>, 
	=?UTF-8?Q?Pavel_Kou=C5=99il?= <pajousek@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c151fa40581c050e8c2663
Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints
From: pierre.php@gmail.com (Pierre Joye)

--001a11c151fa40581c050e8c2663
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Feb 8, 2015 10:52 AM, "Rasmus Lerdorf" <rasmus@lerdorf.com> wrote:
>
> On 02/07/2015 09:51 PM, Andrea Faulds wrote:
> >> tan(1);
> >> echo strstr("test", "est", 1);
> >
> > Banning int->float and float->int is both a pain point and sometimes a
life-saver. It=E2=80=99s annoying that tan(1) doesn=E2=80=99t work. On the =
other hand, you
discover if your ints floats would be silently truncated (as I did with
PictoSwap).
> >
> > I wouldn=E2=80=99t say that int->string not working is a problem, thoug=
h.
Seeing something like strstr(=E2=80=9Ctest=E2=80=9D, =E2=80=9Cest=E2=80=9D,=
 1); is rather confusing.
Looking at it, I=E2=80=99d think the third parameter is some sort of number=
 for you
to want to pass an integer to it. If I want a string, I=E2=80=99ll use one.
>
> This isn't int->string. This is int->boolean. The 3rd arg to strstr() is
> a boolean and passing 1 instead of true makes it blow up. It is very
> very common for people to pass 0 or 1 in place of true/false to all
> sorts of things in PHP.
>
> > Yes, the RFC is somewhat inaccurate in that respect. It is per-file in
one sense (like encoding, but unlike ticks, it has no effect on the
including or included files). However, it technically affects the remainder
of the file, not the whole file.
>
> Well, no, not the remainder of the file either since it can be switched
> again. It only affects the part of the file between declares if there is
> a second one.

For this specific weirdness it should really be fixed somehow, like for
namespace. It has to be used at the top of a file. As it is a compile time
thing, the extra check should not have much impact.

--001a11c151fa40581c050e8c2663--