Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85097
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5506C783.3020207@seld.be>
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>
	<5506C783.3020207@seld.be>
Date: Tue, 17 Mar 2015 09:03:11 +1100
Message-ID: <CAEZPtU5p6Da=hNQ1zCWoWfS+fHRy+nU0LGyZGVwo8pe-eAJiyA@mail.gmail.com>
To: Jordi Boggiano <j.boggiano@seld.be>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0122eb9c2741d505116f04b9
Subject: Re: [PHP-DEV] About declare(strict_types = 1)
From: pierre.php@gmail.com (Pierre Joye)

--089e0122eb9c2741d505116f04b9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mar 16, 2015 11:07 PM, "Jordi Boggiano" <j.boggiano@seld.be> wrote:
>
> On 16/03/2015 11:49, Pavel Kou=C5=99il wrote:
>>
>> it's similiar to the safe_mode though. Sure, it's not as bad as INI
>> setting, but the "intent" is the same - a switch changing how code
>> behaves.
>
>
> ini_set('memory_limit', 10); also changes how your code behave, but it's
global so that can be problematic.
>
> die; changes how your code behave, but you can fix it if it doesn't do
what you want in your file.
>
> Code has meaning and therefore code changes what the program does. I
don't think that's really a problem.
>
>
>> When I talked about the Dual Mode with some friends who are userland
>> PHP devs (either current or former, because they switched to other
>> stuff), none of them called the Dual Mode a great idea. The responses
>> I got were mostly along the lines of "wow, this seems really weird" to
>> "WTF are those developers smoking". Everyone of them (sure, ~10 people
>> isn't really representative number) said that they think PHP needs
>> STH, but not this Dual Mode stuff.
>>
>> Seriously, think about it for a while - when some setting that changes
>> how code behaves was a good idea?
>
>
> All your friends can happily ignore strict mode and no sysadmin can
enable it as it is per-file. Those of us that do understand it and might
want to use it can do so, and if your friends eventually go beyond the
"this seems really weird" phase (it *is* weird because it's an uncommon
approach to have both strict and non-strict in one language, but that
doesn't necessarily mean it's bad) maybe they'll want to use it too some
day. Or perhaps they'll need to start smoking.

Btw, I have seen similar comment (to the ones in this thread) about the
windows-like separator for namespaces. Guess what? Nobody cares now. :)

--089e0122eb9c2741d505116f04b9--