Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50088 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37281 invoked from network); 2 Nov 2010 22:14:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Nov 2010 22:14:59 -0000 Authentication-Results: pb1.pair.com smtp.mail=ar@ez.no; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=ar@ez.no; sender-id=unknown Received-SPF: error (pb1.pair.com: domain ez.no from 74.125.82.54 cause and error) X-PHP-List-Original-Sender: ar@ez.no X-Host-Fingerprint: 74.125.82.54 mail-ww0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:34955] helo=mail-ww0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C7/00-36874-06D80DC4 for ; Tue, 02 Nov 2010 17:14:59 -0500 Received: by wwb34 with SMTP id 34so178132wwb.11 for ; Tue, 02 Nov 2010 15:14:53 -0700 (PDT) Received: by 10.227.127.142 with SMTP id g14mr17492492wbs.200.1288735696408; Tue, 02 Nov 2010 15:08:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.145.133 with HTTP; Tue, 2 Nov 2010 15:07:55 -0700 (PDT) In-Reply-To: References: <4CCB6B21.1070708@codeangel.org> Date: Tue, 2 Nov 2010 23:07:55 +0100 Message-ID: To: Felipe Pena Cc: Richard Lynch , internals@lists.php.net Content-Type: multipart/alternative; boundary=0016364ef16a64d3df049419294f Subject: Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON From: ar@ez.no (=?UTF-8?B?QW5kcsOpIFLDuG1ja2U=?=) --0016364ef16a64d3df049419294f Content-Type: text/plain; charset=UTF-8 On Mon, Nov 1, 2010 at 9:47 PM, Felipe Pena wrote: > 2010/11/1 Richard Lynch > > > On Fri, October 29, 2010 7:47 pm, admin wrote: > > > WTF is T_PAAMAYIM_NEKUDOTAYIM? > > > > > > This has to be THE most asked question by new php developers when they > > > come across it. Can we please change the token name to T_DOUBLE_COLON > > > so I don't have to hear about it constantly? > > > > > > Those that disagree don't do enough PHP support to know how often it > > > is > > > asked. it's worth it. > > > > -1 > > > > > Instead of renaming the token, I prefer to associate a literal string to > each token, to have a legible error message, without the T_ being shown. > > For example, we could use in the Bison grammar file: > %token T_PAAMAYIM_NEKUDOTAYIM "::" > > So that the error message become: > > $ sapi/cli/php -r '::' > Parse error: syntax error, unexpected :: in Command line code on line 1 > > Instead of the known "unexpected T_PAAMAYIM_NEKUDOTAYIM" one. > +1 on implementing this so we don't have to wait for lemon. While knowing how to use a search engine is good, it's even better to not have to and save the time spent on it. > -- > Regards, > Felipe Pena > --0016364ef16a64d3df049419294f--