Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84714
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender)
MIME-Version: 1.0
Sender: kobrasrealm@gmail.com
Date: Fri, 13 Mar 2015 15:51:30 -0400
Message-ID: <CAPKwhws-o7Z-k9zwDW9qPEMw=vKaNP9YM1yXtWM+wR5qjwBzGQ@mail.gmail.com>
To: "inter >> PHP internals" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0103eb52a43e50051130d3c3
Subject: Re: A plea for unity on scalar types
From: scott@arciszewski.me (Scott Arciszewski)

--089e0103eb52a43e50051130d3c3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

 Pavel_Kou=C5=99il wrote:

> - It is a "setting" that changes the language's behavior; I don't
> think that it matters whether or not it would be an INI setting or the
> declare() one, because both of them are bad.
>
> It allows people who want strict typing to declare it on a per-PHP-file
basis. An INI setting cannot offer this guarantee. This is required if weak
and strict are to be both supported.

> - It does not "unite different usages of PHP into a single group"; it
> does exactly the opposite, splitting PHP usage into TWO groups.
>
> It also allows the two groups to work together rather than forking PHP
into separate languages: PHPstrict and PHPweak.

> - Once this dual mode would be introduced to PHP, there would probably
> be no way of removing it later without massive BC break, once most
> people would realize that it is really awful to have it in the
> language.
>
> What is "really awful" about this? Moving forward, everything could move
towards strict typing. I could see PHP 8 or 9 having strict be the default,
if everyone wanted that. And then the declare() being deprecated and
removed as major versions increase.

Scott

--089e0103eb52a43e50051130d3c3--