Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123674
Precedence: bulk
MIME-Version: 1.0
References: <CAPzBOBMidokE3xw251f+_qbCPAyQQRcN1WnyVF0xfuzaPBU3JA@mail.gmail.com>
 <CA+p1FaboniOZWXy4UYK1BxvO+WfwYKpndVCCcWFJHTCQUm_jkQ@mail.gmail.com>
In-Reply-To: <CA+p1FaboniOZWXy4UYK1BxvO+WfwYKpndVCCcWFJHTCQUm_jkQ@mail.gmail.com>
Date: Wed, 19 Jun 2024 14:04:16 +0200
Message-ID: <CABdc3WqaJ9nRSjsRu=vcXr5EADFjYM-zMbPLzAfngGPQzOXP+w@mail.gmail.com>
Subject: Re: [PHP-DEV] Renaming "strict types" to "scalar type coercion"
To: David Gebler <davidgebler@gmail.com>
Cc: Robert Landers <landers.robert@gmail.com>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000bb203061b3d007f"
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--0000000000000bb203061b3d007f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi David, Robert,

wt., 18 cze 2024 o 23:12 David Gebler <davidgebler@gmail.com> napisa=C5=82(=
a):

> ...
> If I were to support any change to how this feature works for PHP 9, I
> think it would be providing a mechanism to enable it for all files at onc=
e,
> maybe either via a .ini setting such as strict_types_default=3D1 or a new
> declare which applies to all files included or autoloaded from that point
> on, i.e. a declare that could be used as the first line of an entrypoint
> script to make all files in a project have strict typing mode
> enabled/disabled (unless a particular file overrides for its own scope wi=
th
> its own declare).
>
> Changing the name to anything other than what it is now, with or without
> flipping the value, just seems like a major BC headache for no gain.
>

I share a similar opinion here.
I'd also rather see a proposal that enables setting the declares outside of
PHP files as this is mostly the same line for every file in most codebases
I work with.

# name it `.phpdeclare` in the execution directory or places where certain
PHP files are read by the PHP interpreter, whatever
```ini
# Global default directives
[*.php]
strict_types =3D 1
ticks =3D 0
encoding =3D UTF-8

# Directives for specific directories
[src/*.php]
strict_types =3D 1

[tests/*.php]
strict_types =3D 0

# Directives for specific files
[scripts/setup.php]
strict_types =3D 1
ticks =3D 1
```

Just an example, shoving some declares can be set using glob-like patterns
or specific files.
I see potential in this kind of declaring these directives for future
extensions.
This is something I'd love to consider instead of just renaming things we
already have.

Cheers,
Micha=C5=82 Marcin Brzuchalski

--0000000000000bb203061b3d007f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi David, Robert,</div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">wt., 18 cze 2024 o 23:12=
=C2=A0David Gebler &lt;<a href=3D"mailto:davidgebler@gmail.com">davidgebler=
@gmail.com</a>&gt; napisa=C5=82(a):<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"auto"><div><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">...</div></div></div><div dir=3D"auto">If =
I were to support any change to how this feature works for PHP 9, I think i=
t would be providing a mechanism to enable it for all files at once, maybe =
either via a .ini setting such as strict_types_default=3D1 or a new declare=
 which applies to all files included or autoloaded from that point on, i.e.=
 a declare that could be used as the first line of an entrypoint script to =
make all files in a project have strict typing mode enabled/disabled (unles=
s a particular file overrides for its own scope with its own declare).</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">Changing the name to anythin=
g other than what it is now, with or without flipping the value, just seems=
 like a major BC headache for no gain.</div></div></blockquote><div><br></d=
iv><div>I share a similar opinion here.</div><div>I&#39;d also rather see a=
 proposal that enables setting the declares outside of PHP files as this is=
 mostly the same line for every file in most codebases I work with.</div><d=
iv><br></div><div># name it `.phpdeclare` in the execution directory or pla=
ces where certain PHP files are read by the PHP interpreter, whatever</div>=
<div>```ini</div># Global default directives<br>[*.php]<br>strict_types =3D=
 1<br>ticks =3D 0<br>encoding =3D UTF-8<br><br># Directives for specific di=
rectories<br>[src/*.php]<br>strict_types =3D 1<br><br>[tests/*.php]<br>stri=
ct_types =3D 0<br><br># Directives for specific files<br>[scripts/setup.php=
]<br>strict_types =3D 1<br>ticks =3D 1<br><div>```</div><div><br></div><div=
>Just an example, shoving some declares can be set using glob-like patterns=
 or specific files.</div><div>I see potential in this kind of declaring the=
se directives for future extensions.</div><div>This is something I&#39;d lo=
ve to consider instead of just renaming things we already have.</div><div><=
br></div><div>Cheers,</div><div>Micha=C5=82 Marcin Brzuchalski</div></div><=
/div>

--0000000000000bb203061b3d007f--