Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81629
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.208 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
In-Reply-To: <54CFC849.3080001@gmail.com>
Date: Mon, 2 Feb 2015 19:08:52 +0000
Cc: Pierre Joye <pierre.php@gmail.com>,
 Dmitry Stogov <dmitry@zend.com>,
 PHP Internals <internals@lists.php.net>,
 Nikita Popov <nikita.ppv@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <1C7877DD-1FCC-463C-AECF-C767EE1256F7@ajf.me>
References: <CA+9eiLuueVvYgT-fhCvzBSxzoDioinpc5Eok5OQtGDBG1FZM=w@mail.gmail.com> <CAEZPtU5G1T3mpvjL2U0zAoYUKs8xh6NqjZ+hv9Aeab0h=TRB4A@mail.gmail.com> <54CFC849.3080001@gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Subject: Re: [PHP-DEV] What do we need strict scalar type hints for?
From: ajf@ajf.me (Andrea Faulds)

Hi Stas,

> On 2 Feb 2015, at 18:56, Stanislav Malyshev <smalyshev@gmail.com> =
wrote:
>=20
> Hi!
>=20
>> Keeping that in mind, the declare statement, as ugly as it may look,
>> could be actually a killer to finally get what both camps want but
>> never (and never will) manage to agree.
>=20
> I think having two conceptual frameworks in one language and having to
> deal with (and potentially maintain) code bases with mixed conceptual
> framework is a very bad idea. That would lead to a language
> fragmentation as strict code will become hard to combine with =
non-strict
> code within one application, and pretty soon people will start asking
> questions like "is this library written in strict-PHP or =
non-strict-PHP?
> ow, dang, we can't use it because we use the other one=E2=80=A6"

I don=E2=80=99t see how. This proposal has been specifically designed to =
allow strict and non-strict code to be completely interoperable.

--
Andrea Faulds
http://ajf.me/