Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85035
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.160.179 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAB6YZuxhAGsRrOKTSNF5nt4bwxHSx9B-NakDk9hzPTu0HWTOFA@mail.gmail.com>
References: <CABBJUpfiy1BpdyZ5MJmQb3vQz9U8TkSECHCRctupV+BUG1H=fw@mail.gmail.com>
	<55066F07.80308@birkholz.biz>
	<CABBJUpd+yd_7g8VkU0SHRMt0a35idyyLS_7m6=-cGgBB1RzkQg@mail.gmail.com>
	<CAN=kQJe6civW3x=uT2wMB7Mb-33LvkSyHfU=FfB8cfbWsVE+_A@mail.gmail.com>
	<CAGa2bXaMPs2WNOvJzJz6S3Qm1z28H=msi8SdVsmPYJGz-kM8hQ@mail.gmail.com>
	<5506794B.8090008@birkholz.biz>
	<CAGa2bXbGxr4E8hi1_faNWOWSeLi6kn5kQJknCaZ4vUTNxHR+tg@mail.gmail.com>
	<CAEZPtU68oFYN5YoQk7+kJPDancrfj9eEbau9BCB6OgkQEV7p8Q@mail.gmail.com>
	<CAGa2bXYU4LVDdVdCjRUbqvFbkBzy_U3O21Hu7uarZBK_F=ir8A@mail.gmail.com>
	<alpine.DEB.2.11.1503161120100.4205@whisky.home.derickrethans.nl>
	<CAB6YZuxhAGsRrOKTSNF5nt4bwxHSx9B-NakDk9hzPTu0HWTOFA@mail.gmail.com>
Date: Mon, 16 Mar 2015 12:04:31 +0000
Message-ID: <CA+kxMuQCeki05C8PNQf7_XPc_vPg7_6rvCGfyp2fsRorE1=aTg@mail.gmail.com>
To: =?UTF-8?Q?Pavel_Kou=C5=99il?= <pajousek@gmail.com>
Cc: Derick Rethans <derick@php.net>, Pierre Joye <pierre.php@gmail.com>, 
	PHP internals <internals@lists.php.net>, Dennis Birkholz <dennis@birkholz.biz>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] About declare(strict_types = 1)
From: danack@basereality.com (Dan Ackroyd)

On 16 March 2015 at 11:49, Pavel Kou=C5=99il <pajousek@gmail.com> wrote:
>>>
>
> Seriously, think about it for a while - when some setting that changes
> how code behaves was a good idea?


The problem is that there are two irreconcilable camps - some people
want weak STHs, other people want strict STHs.

This RFC gives both camps what they want, at the cost of having the dual mo=
de.

I personally would prefer a single mode, with strict STHs but I can
see that would piss off the other camp. And so to me, this RFC even
with the ickiness of the setting, is an an acceptable cost to giving
both sides what they want. Oh, and people who don't want to use scalar
type hints at all, can still continue to not use scalar type hints,
and their code will continue to keep working.

Anyone who is voting no, isn't doing so because they are missing out
on a feature, they're doing it to block other people from getting what
they want in PHP, which is just a terrible way to vote.

And if the strict camp are wrong and strict scalars are just not used
by a large proportion of the PHP community, it would be trivial to
remove support for the strict mode in a future version of PHP, as all
code that runs in strict mode, will automatically work in weak mode.

cheers
Dan