Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112915
Content-Type: multipart/alternative; boundary=Apple-Mail-F6C31CEF-5622-4F37-8BD5-3EC0B6B4B1FE
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Sun, 17 Jan 2021 18:02:53 +0100
Message-ID: <85650FC3-F510-4837-8D21-875288EC1EF1@gmail.com>
References: <DM6PR07MB66181E0D6B74EE34AC53F057F9A50@DM6PR07MB6618.namprd07.prod.outlook.com>
Cc: internals@lists.php.net
In-Reply-To: <DM6PR07MB66181E0D6B74EE34AC53F057F9A50@DM6PR07MB6618.namprd07.prod.outlook.com>
To: tyson andre <tysonandre775@hotmail.com>
Subject: Re: [PHP-DEV] Proposal: Render floats differently from integers in print_r()
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail-F6C31CEF-5622-4F37-8BD5-3EC0B6B4B1FE
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



> Le 17 janv. 2021 =C3=A0 16:58, tyson andre <tysonandre775@hotmail.com> a =C3=
=A9crit :
>=20
> =EF=BB=BFHi internals,
>=20
> Currently, print_r() will print ints and floats in exactly the same way, d=
espite the fact that they are different types
> and floats may cause a TypeError (or be treated differently from integers,=
 e.g. avro encoding) when used where an integer is expected.
> This is not documented in https://www.php.net/print_r

This is the same behaviour as `print` (and as`echo`). Note also that there i=
s also no distinction for `print`/`print_r` in rendering the string "1", the=
 integer 1, and the boolean`true`. I think that the original intention of `p=
rint_r` was to have a =E2=80=9Crecursive=E2=80=9D version of `print`.=20

If some action is to be taken, I suggest to deprecate `print_r`.

=E2=80=94Claude=20


--Apple-Mail-F6C31CEF-5622-4F37-8BD5-3EC0B6B4B1FE--