Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50063 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41059 invoked from network); 1 Nov 2010 20:48:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Nov 2010 20:48:10 -0000 Authentication-Results: pb1.pair.com header.from=felipensp@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=felipensp@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: felipensp@gmail.com X-Host-Fingerprint: 209.85.214.42 mail-bw0-f42.google.com Received: from [209.85.214.42] ([209.85.214.42:35841] helo=mail-bw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/EC-10621-9872FCC4 for ; Mon, 01 Nov 2010 15:48:10 -0500 Received: by bwz13 with SMTP id 13so5049580bwz.29 for ; Mon, 01 Nov 2010 13:48:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=fPjBCgNhlp1g+lXuYsMCtb3P4DquHc7aNzhVT4mYsvE=; b=fqtb1SYcHjCgbnUBQuG0wIIPxNGdZHfxPex8JLx2ORcIgmfa7fR7p8Eyj4reu42iPP WJ/lE2huhz+KOVsZKyt0vBWRFOnQGoNoX2HAgGPIYSCCBuZ+N+84H2KrHt2uan+8IAcD szHORJq0OQEcqyBJeJODo5sCG7U0iIo7zobro= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=xugP9OAhLyd8Hz/vaHtr8q/LpRZxZdl7XHZt1U9OVo+gEIexezZPj6/IBdVjj1PeB5 wi44TwAjoTcfOle5+fwY678DEt1yrwJcFKyLvlJfHqSL+gmjKvCbH7SCElwOlwfg7+TQ EDNHTzDQpr/WwO6wqMPad+i2EUoo2Xj3ua9JE= Received: by 10.204.78.81 with SMTP id j17mr7471668bkk.44.1288644487240; Mon, 01 Nov 2010 13:48:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.151.211 with HTTP; Mon, 1 Nov 2010 13:47:46 -0700 (PDT) In-Reply-To: References: <4CCB6B21.1070708@codeangel.org> Date: Mon, 1 Nov 2010 18:47:46 -0200 Message-ID: To: Richard Lynch Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=001485f87d96e75f2d049403ec1d Subject: Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON From: felipensp@gmail.com (Felipe Pena) --001485f87d96e75f2d049403ec1d Content-Type: text/plain; charset=UTF-8 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. -- Regards, Felipe Pena --001485f87d96e75f2d049403ec1d--