Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80536
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <54B6FBD8.9050109@gmail.com>
Date: Thu, 15 Jan 2015 14:03:30 +0000
Cc: Zeev Suraski <zeev@zend.com>,
 RQuadling@gmail.com,
 Leigh <leight@gmail.com>,
 PHP Internals List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <20CF60F6-EADC-4174-8C71-163B4651447A@ajf.me>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> <CAPwsocGyv7dp8n=_E1QfrXRSbYZXcHZAPk5F=hDLB070i=SCGA@mail.gmail.com> <4E2073DE-0951-498C-97BB-DDAC094F11FA@ajf.me> <9a033dd1f223f854e760924d118ab812@mail.gmail.com> <CAKUjMCU-57cDpG5ZbDGv10dSqx=Ey40D-WbKxKSnC6oSYOfLWw@mail.gmail.com> <2ae0164cb9b9bf1c974d7a3c60af0466@mail.gmail.com> <54B6FBD8.9050109@gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: ajf@ajf.me (Andrea Faulds)

Hi Stas,

> On 14 Jan 2015, at 23:29, Stanislav Malyshev <smalyshev@gmail.com> =
wrote:
>=20
> I agree. Being wrong is bad, making a mistake is bad, but having split
> personality language and not knowing in which world you are - or even
> worse, having to deal with both worlds in the same code and being =
thrown
> back and forth between them by some little switch which is easy to =
miss
> - IMO is worse. I don't like strict typing in PHP because I think it =
is
> contrary to the idea of how dynamic languages should work, but I'd
> rather have that then two sets of rules living within the same code,
> especially when looking at the function I can't even know how it would
> work without checking if there's a declare hiding somewhere. And
> refactoring becomes a nightmare - what if I moved function from strict
> world to non-strict world or vice versa?

It=E2=80=99s not about the location of the function, but the call site. =
You can place a function anywhere and it will behave identically.

> I also agree with Dmitry in other thread - if some conv rules are so =
bad
> everybody hates them (or at least you think it is the case :), we can
> change them. We are already on that track with some weird ones like
> array->string. Even with BC effects, IMO better than too many sets of
> rules.

There are some minor issues with the conversion rules that could be =
fixed, but a lot of people have a problem not just with the conversion =
rules, but with the implicit conversion itself. The previous RFC (Scalar =
Type Hinting with Casts) wasn=E2=80=99t popular with many people for =
that reason: sure, it had stricter rules, but that won=E2=80=99t please =
people who want no conversion whatsoever.

Thanks.
--
Andrea Faulds
http://ajf.me/