Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90037
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.215.66 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <568B0C84.7060802@gmail.com>
References: <CAESVnVoJBRF3VfKrnWGNCah3KAbxwjacPAwR1HZUC-T-vN=KDQ@mail.gmail.com>
	<568B0C84.7060802@gmail.com>
Date: Mon, 4 Jan 2016 18:00:53 -0800
Message-ID: <CAESVnVpfq_VM8b7pPnZjkQsddGKV9Wis9YBwpzXKVtx4-6-VwQ@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Normalize token_get_all() output (with flag)
From: pollita@php.net (Sara Golemon)

On Mon, Jan 4, 2016 at 4:21 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> I think it's a great idea, token_get_all() is annoying
> to deal with. We'd have to fix token_name though so that this would
> still work:
>
Ah, excellent point!

> We could, of course, do something like
> $token[0]<=255?$token[0]:token_name($token[0]) - but that looks hacky.
>
Do you mean have users of the API do that? Or have the implementation
of token_name() do that?  Because the latter doesn't seem unreasonable
at all.

For example:
var_dump(token_name(ord(';'))); // string(1)";"

-Sara