Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108952
MIME-Version: 1.0
References: <CAF+90c8xHmxy9DL2cdqc3beNquJ=A6z0+RB8ggwZ6v+a1ixFuw@mail.gmail.com>
 <1715830.3Z3xILz1Hf@mcmic-probook>
In-Reply-To: <1715830.3Z3xILz1Hf@mcmic-probook>
Date: Tue, 10 Mar 2020 15:53:41 +0100
Message-ID: <CAF+90c_uK4k_sg8RgG5JWZAwbJz+gEqvA7c1kaEDUtcfVWTmiA@mail.gmail.com>
To: =?UTF-8?Q?C=C3=B4me_Chilliet?= <come.chilliet@fusiondirectory.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001c1f4d05a0814a08"
Subject: Re: [PHP-DEV] [VOTE] Object-based token_get_all() alternative
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000001c1f4d05a0814a08
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 10, 2020 at 12:36 PM C=C3=B4me Chilliet <
come.chilliet@fusiondirectory.org> wrote:

> Hello,
>
> I know I=E2=80=99m late, but shouldn't these tokens have a __toString() m=
ethod?
> It=E2=80=99s not listed in rejected features.
>

Would __toString() return $token->text? I'm not strictly opposed to this,
but I'd be hard pressed to think of a situation where I would prefer
writing (string) $token over $token->text. Generally, the less magic the
better :)

Nikita

--0000000000001c1f4d05a0814a08--