Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90047 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80319 invoked from network); 5 Jan 2016 03:38:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 03:38:11 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.52 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.220.52 mail-pa0-f52.google.com Received: from [209.85.220.52] ([209.85.220.52:34732] helo=mail-pa0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C9/0C-07292-3AA3B865 for ; Mon, 04 Jan 2016 22:38:11 -0500 Received: by mail-pa0-f52.google.com with SMTP id uo6so187985969pac.1 for ; Mon, 04 Jan 2016 19:38:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=vgstJjsNal3G11+5evPhFojFlDie6f1bGrVCfpYQXZg=; b=i1B/kSRbNLx+6dehSoKde450ZwfznvnWbbAkmz5HPlY6zxG3rEMWeuAaoZjmB27zF+ sXKR9rLDlleULTnQzS4kjn4wuUiQtvweuC11Efhq2a75wJogWShzFxwKaITK5Ufcmq6B lvJkEptJlrhKZBmJ2ghiRhBKVSUTp54eBloxQi9n3Rp6Vt9PaEfIlzdZf+YJeyn34aIY v/AnU+dBynN5jRBH9tim1H/XcMV8Dr9UI6gZyDZS9QDojbcWdnfQTn8bfLw7F5ZudZj4 +bOkeG8iu1jnQGWKGUiu91z08eUCDhLtxlD1g8CfAk7rG2cT+/z07fLHMvnRjh/LX52g /u5Q== X-Received: by 10.66.253.97 with SMTP id zz1mr88685691pac.106.1451965088537; Mon, 04 Jan 2016 19:38:08 -0800 (PST) Received: from stas-air.corp.wikimedia.org (tan1.corp.wikimedia.org. [198.73.209.1]) by smtp.gmail.com with ESMTPSA id sv8sm129321285pab.13.2016.01.04.19.38.07 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jan 2016 19:38:07 -0800 (PST) To: Sara Golemon References: <568B0C84.7060802@gmail.com> Cc: PHP internals Message-ID: <568B3A9E.7000505@gmail.com> Date: Mon, 4 Jan 2016 19:38:06 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Normalize token_get_all() output (with flag) From: smalyshev@gmail.com (Stanislav Malyshev) Hi! >> 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. I meant for token_name() to do that internally, so that the user can use just token_name() instead of boilerplate code. Sorry for not being clear. > For example: > var_dump(token_name(ord(';'))); // string(1)";" Yes, exactly. -- Stas Malyshev smalyshev@gmail.com