Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127981
Message-ID: <7808C18B-127F-4C60-914C-CCF14FD74055@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_38645F5C-3199-4306-8093-39E4436FEC0D"
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: Wed, 9 Jul 2025 23:23:04 +0200
In-Reply-To: <6dxtR-lrZ-CVEhWWJp1IlCYt8_v0u16-lWG69EeyJAvUQdlDeW-2VgKZ7tezX4fG-JhORVaXZa9Kotnm8WlM6Mz7G1_NzzhFSozx3wuEHTU=@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>
From: claude.pache@gmail.com (Claude Pache)


--Apple-Mail=_38645F5C-3199-4306-8093-39E4436FEC0D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 9 juil. 2025 =C3=A0 14:21, Gina P. Banyard <internals@gpb.moe> a =
=C3=A9crit :
>=20
> On Wednesday, 9 July 2025 at 08:17, Daikaras <webmaster@daikaras.lt> =
wrote:
>>=20
>>> We propose to deprecate the following non-standard cast names:
>>>=20
>>> (integer)
>>> (boolean)
>>> (double)
>>> (binary)
>> Hello,
>>=20
>> Just wondering is this going to affect `settype()` function? There is =
already some disparity in that `settype()` supports =
`integer/boolean/double` but not `binary` type (and additionally =
supports `null` type).
>>=20
> I wasn't aware of the discrepencies with settype() so I added the =
deprecation of non-canonical type names to settype() as its own =
deprecation entry in the ext/standard section.
> Thanks for bringing this to my attention!
>=20
> Best regards,
>=20
> Gina P. Banyard

Hi,

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):

```php
function settype_from(&$a, &b) {
    return settype($a, gettype($b));
}
```

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).


=E2=80=94Claude=

--Apple-Mail=_38645F5C-3199-4306-8093-39E4436FEC0D
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 9 juil. 2025 =C3=A0 14:21, 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;" =
class=3D"protonmail_signature_block"><div class=3D"protonmail_quote">On =
Wednesday, 9 July 2025 at 08:17, Daikaras &lt;webmaster@daikaras.lt&gt; =
wrote:<br>
        <blockquote class=3D"protonmail_quote" type=3D"cite">
           =20
    <br>
    <blockquote type=3D"cite"><p>
        We propose to deprecate the following non-standard cast names:
      </p>
      <ul>
        <li class=3D"level1">
          <div class=3D"li"> <code class=3D"code php"><span =
class=3D"br0">(</span>integer<span class=3D"br0">)</span></code></div>
        </li>
        <li class=3D"level1">
          <div class=3D"li"> <code class=3D"code php"><span =
class=3D"br0">(</span>boolean<span class=3D"br0">)</span></code></div>
        </li>
        <li class=3D"level1">
          <div class=3D"li"> <code class=3D"code php"><span =
class=3D"br0">(</span>double<span class=3D"br0">)</span></code></div>
        </li>
        <li class=3D"level1">
          <div class=3D"li"> <code class=3D"code php"><span =
class=3D"br0">(</span>binary<span class=3D"br0">)</span></code></div>
        </li>
      </ul>
    </blockquote><p>Hello,</p><p>Just wondering is this going to affect =
`settype()` function?
      There is already some disparity in that `settype()` supports
      `integer/boolean/double` but not `binary` type (and additionally
      supports `null` type).</p>
 =20


        </blockquote><span></span><div>I wasn't aware of the =
discrepencies with settype() so I added the deprecation of non-canonical =
type names to settype() as its own deprecation entry in the ext/standard =
section.</div><div>Thanks for bringing this to my =
attention!</div><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></blockquote></div><br><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><div><br></div><div><br></div><div>=E2=80=94Claude</div></body></=
html>=

--Apple-Mail=_38645F5C-3199-4306-8093-39E4436FEC0D--