Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50075
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        b=uK+i5QucUcPVt8GQLpvFSPmSRzOrNV/mxn8tBSF+oc9E4L2k6YP9kQvUl29K0MZVB3
         ocnDP7NrpiOYUZyfcV7s33f4cJ8E8ePQkaknq0GEX64k56ixW2pKb3H6yTnZbEOsDOmY
         yZExR6d+0tOcmozbQ2f17tiqVUJMHuEUdT2T0=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <4CCF27FF.1000305@lerdorf.com>
References: <4CCB6B21.1070708@codeangel.org>
	<c21d768d4b0c18b5ba145b0f04f0dd00.squirrel@www.l-i-e.com>
	<AANLkTimD8eJb2p-VZP4c9vQb=VJ=Z3+fRv1XO5uSh8dL@mail.gmail.com>
	<4CCF27FF.1000305@lerdorf.com>
Date: Tue, 2 Nov 2010 07:18:03 +0100
Message-ID: <AANLkTi=K_D_ewsGJ4GdNjDY92QWTLV+4hDDpdy5GsZ2n@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Felipe Pena <felipensp@gmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=00163631084327e99f04940be395
Subject: Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON
From: info@tyrael.hu (Ferenc Kovacs)

--00163631084327e99f04940be395
Content-Type: text/plain; charset=UTF-8

On Mon, Nov 1, 2010 at 9:50 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 11/1/10 1:47 PM, Felipe Pena wrote:
> > 2010/11/1 Richard Lynch <ceo@l-i-e.com>
> >
> >> 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.
>
> Years and years ago that was the intent.  I didn't think there was a
> clean way to do that in yacc though.
>
>
...
so when will we start replacing the tokens with  literals?

Tyrael

--00163631084327e99f04940be395--