Newsgroups: php.internals,php.internals
Path: news.php.net
Xref: news.php.net php.internals:128126 php.internals:128127
Message-ID: <4CE76107-60FD-433B-B577-F0C9FF8F3A19@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_315E2683-5FB9-4D09-A494-078A132F5CE3"
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 8.5
Date: Fri, 18 Jul 2025 21:38:57 +0200
In-Reply-To: <kQ57WxqZ3Td_wHtZ0XvstiTycj9HjIvh6arIzYmGG48Woheaabg1kS5CZ_W82D_6JFu_0rHaAGUChPOPrX8OtPrbG7m0K0jD2jJbYVLctB0=@gpb.moe>
Cc: Daikaras <webmaster@daikaras.lt>,
 PHP internals <internals@lists.php.net>
To: "Gina P. Banyard" <internals@gpb.moe>
References: <hzKdzBWWITU1ePjv3qcyK-OzroFAkWst9MQBw2zvKSA8pk1iqruLZZWTTh9gYDo2QX8EY_PiirVYDuwne2Upr3GlqZk570wtLOF49aaP-HQ=@gpb.moe>
 <43b55cf7-bd7a-40a0-90ee-0b9dd67f54bb@daikaras.lt>
 <6dxtR-lrZ-CVEhWWJp1IlCYt8_v0u16-lWG69EeyJAvUQdlDeW-2VgKZ7tezX4fG-JhORVaXZa9Kotnm8WlM6Mz7G1_NzzhFSozx3wuEHTU=@gpb.moe>
 <7808C18B-127F-4C60-914C-CCF14FD74055@gmail.com>
 <kQ57WxqZ3Td_wHtZ0XvstiTycj9HjIvh6arIzYmGG48Woheaabg1kS5CZ_W82D_6JFu_0rHaAGUChPOPrX8OtPrbG7m0K0jD2jJbYVLctB0=@gpb.moe>
From: claude.pache@gmail.com (Claude Pache)


--Apple-Mail=_315E2683-5FB9-4D09-A494-078A132F5CE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 10 juil. 2025 =C3=A0 13:18, Gina P. Banyard <internals@gpb.moe> a =
=C3=A9crit :
>=20
> On Wednesday, 9 July 2025 at 22:26, Claude Pache =
<claude.pache@gmail.com> wrote:
>> Hi,
>>=20
>> A possible reason for wanting to use the non-canonical names in =
settype(), is that those names are returned by gettype(). Fictional =
example (not intended to be reasonable, only illustrative):
>>=20
>> ```php
>> function settype_from(&$a, &b) {
>>     return settype($a, gettype($b));
>> }
>> ```
>>=20
>> Personally, I have used "integer", etc. instead  of "int", etc., in =
settype() in the past, because those were the =E2=80=9Ccanonical=E2=80=9D =
(as I perceived) forms returned by gettype(). I have slowly fallen out =
of that habit in the years after I began to use scalar type declarations =
(introduced in PHP 7).
>=20
> We are well aware of this "issue" and get_debug_type() was introduced =
in PHP 8 as a replacement for gettype() that returns the canonical =
names.
> The one difference is that objects return the class name rather than =
"object".
> I can add a deprecation of gettype() to nudge people to use =
get_debug_type() instead, if you think that's reasonable.
>=20
> Best regards,
>=20
> Gina P. Banyard

Hi,

Sorry for having forgotten to answer to this point. To be clearer, I =
think it is fine for `settype()` to keep support for the legacy names =
("integer", "boolean", etc.) returned by `gettype()`, even if we =
deprecate the syntax `(integer) $x`, etc. The syntax `(integer)` is =
trivial to correct with a simple search-and-replace; such a correction =
is not straightforward for `settype($a, $type)` as $type is not =
necessarily a literal string. Moreover, the $type argument in =
`settype()` is not confusable with hypothetical user-defined types =
named, e.g., `integer`, as user-defined types are forbidden in =
`settype()` anyway.

=E2=80=94Claude=

--Apple-Mail=_315E2683-5FB9-4D09-A494-078A132F5CE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;"><br =
id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>Le 10 juil. 2025 =C3=A0 13:18, Gina P. Banyard =
&lt;internals@gpb.moe&gt; a =C3=A9crit :</div><br =
class=3D"Apple-interchange-newline"><div><div style=3D"font-family: =
Arial, sans-serif; font-size: 14px;"><div class=3D"protonmail_quote">On =
Wednesday, 9 July 2025 at 22:26, Claude Pache =
&lt;claude.pache@gmail.com&gt; wrote:<br><blockquote =
class=3D"protonmail_quote" =
type=3D"cite"><div>Hi,</div><div><br></div><div>A possible reason for =
wanting to use the non-canonical names in settype(), is that those names =
are returned by gettype(). Fictional example (not intended to be =
reasonable, only =
illustrative):</div><div><br></div><div>```php</div><div>function =
settype_from(&amp;$a, &amp;b) {</div><div>&nbsp; &nbsp; return =
settype($a, =
gettype($b));</div><div>}</div><div>```</div><div><br></div><div>Personall=
y, I have used "integer", etc. instead &nbsp;of "int", etc., in =
settype() in the past, because those were the =E2=80=9Ccanonical=E2=80=9D =
(as I perceived) forms returned by gettype(). I have slowly fallen out =
of that habit in the years after I began to use scalar type declarations =
(introduced in PHP 7).</div></blockquote><div><br></div><div>We are well =
aware of this "issue" and&nbsp;<span>get_debug_type</span>() was =
introduced in PHP 8 as a replacement for gettype() that returns the =
canonical names.</div><div>The one difference is that objects return the =
class name rather than "object".</div><div>I can add a deprecation of =
gettype() to nudge people to use&nbsp;<span>get_debug_type</span>() =
instead, if you think that's =
reasonable.<span></span><div><br></div><div>
    <div>
        <div style=3D"background-color: rgb(255, 255, 255);"><span =
style=3D"font-family:Verdana, sans-serif">Best regards,</span></div><div =
style=3D"background-color: rgb(255, 255, 255);"><br></div><span =
style=3D"background-color: rgb(255, 255, 255);"><span =
style=3D"font-family:Verdana, sans-serif">Gina P. =
Banyard</span></span></div></div></div></div></div></div></blockquote></di=
v><br><div>Hi,</div><div><br></div><div>Sorry for having forgotten to =
answer to this point. To be clearer, I think it is fine for `settype()` =
to keep support for the legacy names ("integer", "boolean", etc.) =
returned by `gettype()`, even if we deprecate the syntax `(integer) $x`, =
etc. The syntax `(integer)` is trivial to correct with a simple =
search-and-replace; such a correction is not straightforward for =
`settype($a, $type)` as $type is not necessarily a literal string. =
Moreover, the $type argument in `settype()` is not confusable with =
hypothetical user-defined types named, e.g., `integer`, as user-defined =
types are forbidden in `settype()` =
anyway.</div><div><br></div><div>=E2=80=94Claude</div></body></html>=

--Apple-Mail=_315E2683-5FB9-4D09-A494-078A132F5CE3--