Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69187 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68653 invoked from network); 18 Sep 2013 12:30:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Sep 2013 12:30:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=nicolas.grekas@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=nicolas.grekas@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.46 as permitted sender) X-PHP-List-Original-Sender: nicolas.grekas@gmail.com X-Host-Fingerprint: 209.85.212.46 mail-vb0-f46.google.com Received: from [209.85.212.46] ([209.85.212.46:35837] helo=mail-vb0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 38/75-43258-6EC99325 for ; Wed, 18 Sep 2013 08:30:31 -0400 Received: by mail-vb0-f46.google.com with SMTP id p13so5055551vbe.5 for ; Wed, 18 Sep 2013 05:30:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=vYlNmcr/fp51j7FiwgPHoxm5TJ0Dcu+E/nlHUoWQaAw=; b=uPI3hVui5UFutB9cwl/Hvj3UA9OleLnZWFLHws4GSCc0bXXD2m1rOIDrWkmNtfya/2 7TS6uRSnJnYr7j3/izCZLu33gEjn9ZHsY9BwyuTlBSyWVSfkLe1sUjqS5lMn2GqkJNLR 84smKLoPLaBgOSwzlr4lit6jnUDVmNw9M/+A6aSlVs+VHWyg9x6wl6qdDDnTk9p4StjD aPghDlg/N24OAXS0bVTBSTBMOKqBLg3aqIaMghugMPTU7z86Me/sDCttDhyxncc41izp l93zzjpywdyZQdkRA51hVEDEjwGX4ZUNV4C31eEVn3gfM1wdj+AYl6k+0O0C4zdI5me5 ckAA== X-Received: by 10.52.230.233 with SMTP id tb9mr31118073vdc.17.1379507427917; Wed, 18 Sep 2013 05:30:27 -0700 (PDT) MIME-Version: 1.0 Sender: nicolas.grekas@gmail.com Received: by 10.52.249.80 with HTTP; Wed, 18 Sep 2013 05:30:07 -0700 (PDT) In-Reply-To: References: Date: Wed, 18 Sep 2013 14:30:07 +0200 X-Google-Sender-Auth: IwHn7onCxdHSXLSp5u70Hk1dEfk Message-ID: To: Bob Weinand Cc: Developers PHP Mailing List Content-Type: multipart/alternative; boundary=089e0111afaa34edef04e6a79a60 Subject: Re: [PHP-DEV] [RFC] Keywords as identifiers From: nicolas.grekas+php@gmail.com (Nicolas Grekas) --089e0111afaa34edef04e6a79a60 Content-Type: text/plain; charset=ISO-8859-1 Hi Bob, thanks for the RFC! For those of us that use token_get_all(), will the newly allowed token appear as T_STRING or as T_%KEYWORD%? May I suggest you add a word about it in the RFC? As Ryan pointed out in the other thread, a T_%KEYWORD% has a high chance to break existing documentation generators or code parsers. As Nikita remembered us, "default" in $a->default is emitted as a T_STRING. It might be consistent to also emit a T_STRING on the new cases that you plan to allow? Regards, Nicolas --089e0111afaa34edef04e6a79a60--