Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128292
Precedence: bulk
MIME-Version: 1.0
References: <ClHWqZ8xQp5NMLvOxMZ80CqdIr0QVhrCzJmDZyw0h7Z4CtK3DG8fW3dKbf4fu-WJRxvqBY9S_W29um3mHEaGJ9ee1epItOizujB3CpbNKfA=@gpb.moe>
 <EYKUX_e3wzCF2eOwU5beLQfcpz-0w4K1M5fjdITFJ0yND11XWgFm-bI_zh7hz8sNygSLrRLe8sTWz_vpcXPlq5o83R5QKfI_zxNzMu1w9eU=@gpb.moe>
 <3b303d303708b13a2de81dc07753da3a@bastelstu.be> <qHqe_cprXfMx8PAHwaMVUGmJWu94iC0thiRRjwn_hesackCjF6vbZXLie269X7_4AdHcs9By6j_gZX0L6E5aGjHctUCUESFPbC1sDLHd4EE=@gpb.moe>
 <CAPyj-LC03m4RmxBpZJSOdX3EStPRJu2BrRzE971kn-cyZLmHDw@mail.gmail.com>
 <-EPNf2A21qLIrIyEvNmQxV_tNTa1IO5hU-LHGBhjfnVRB33qiwK3yhVV7AxDKSTDUl9ihRpapZLckSgnCn7t9RvUj9Jbtjnx1VLYqCQO6BI=@gpb.moe>
 <2338ef4d-e9d3-4b16-9b52-8d343976d06d@app.fastmail.com>
In-Reply-To: <2338ef4d-e9d3-4b16-9b52-8d343976d06d@app.fastmail.com>
Date: Tue, 29 Jul 2025 14:16:12 +0300
Message-ID: <CAAwdEzAP1khsfd21rZa-CSyWkQYAsDnLSrWM8AWvH2jhkGX8Wg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Warnings for PHP 8.5
To: Rob Landers <rob@bottled.codes>
Cc: "Gina P. Banyard" <internals@gpb.moe>, Ilija Tovilo <tovilo.ilija@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000363d2e063b0f8afe"
From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=)

--000000000000363d2e063b0f8afe
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 29, 2025 at 12:18=E2=80=AFPM Rob Landers <rob@bottled.codes> wr=
ote:

>
> I am not sure that (int)"INF" or (int)"NAN" is misbehaving.
> (int)"Password" also produces `0`, and these are strings. If we had the
> time to discuss it properly, I would argue that simply warning when casti=
ng
> a string to int is the most sensible thing, just like we get an error whe=
n
> coercing a string to int, which is more consistent across the language th=
an
> just special casing some strings.
>
>
>
This is about INF and NAN, the float values, not the strings "INF" and
"NAN".
https://3v4l.org/fAFn3

-- Alex

--000000000000363d2e063b0f8afe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote gmail=
_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 29, 202=
5 at 12:18=E2=80=AFPM Rob Landers &lt;rob@bottled.codes&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u><div><div><br></d=
iv><div>I am not sure that (int)&quot;INF&quot; or (int)&quot;NAN&quot; is =
misbehaving. (int)&quot;Password&quot; also produces `0`, and these are str=
ings. If we had the time to discuss it properly, I would argue that simply =
warning when casting a string to int is the most sensible thing, just like =
we get an error when coercing a string to int, which is more consistent acr=
oss the language than just special casing some strings.</div><div><br></div=
><div id=3D"m_-6787851740426474125sig121229152"><br></div></div></blockquot=
e><div><br></div><div>This is about INF and NAN, the float values, not the =
strings &quot;INF&quot; and &quot;NAN&quot;.<br><a href=3D"https://3v4l.org=
/fAFn3">https://3v4l.org/fAFn3</a></div><div><br>-- Alex=C2=A0</div></div><=
/div>

--000000000000363d2e063b0f8afe--