Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50077
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 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=HP5eEQgQ5OBu2I1QzmV7oRcuw2cRWN8ldvC7/5dbFD+uH/viC2mqH6Zgm9kM2JdjRK
         8HXN8zfXwjQFm+xp6+nGkTRP9RG78JE6X+BSn6bXjwoYwz9QUWitWT39S/FqNg/WyaW1
         we/C61rbdebxcA3FRGR9w7c3cjlMzmfXCwwVw=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <AANLkTimD8eJb2p-VZP4c9vQb=VJ=Z3+fRv1XO5uSh8dL@mail.gmail.com>
References: <4CCB6B21.1070708@codeangel.org>
	<c21d768d4b0c18b5ba145b0f04f0dd00.squirrel@www.l-i-e.com>
	<AANLkTimD8eJb2p-VZP4c9vQb=VJ=Z3+fRv1XO5uSh8dL@mail.gmail.com>
Date: Tue, 2 Nov 2010 07:48:24 +0100
Message-ID: <AANLkTi=kOavetk-Kv=OLNxVTuTnYry6SvXLm6ktBByOB@mail.gmail.com>
To: Felipe Pena <felipensp@gmail.com>
Cc: Richard Lynch <ceo@l-i-e.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=0016364d27a5b2689c04940c4fee
Subject: Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON
From: info@tyrael.hu (Ferenc Kovacs)

--0016364d27a5b2689c04940c4fee
Content-Type: text/plain; charset=UTF-8

On Mon, Nov 1, 2010 at 9:47 PM, Felipe Pena <felipensp@gmail.com> 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.
>
>
>
Thanks Felipe, you are my hero.
Anybody else thinks that this thread is very similar to the last array
dereferencing discussion?
http://www.mail-archive.com/internals@lists.php.net/msg46789.html

Somebody brought up the idea, most of the veterans tried to dismiss without
discussion, pointing out, that its an old topic, and nothing will change,
status quo, others tried to bend the thread to the lemon patch.
and Felipe solved the original problem that everybody thought impossible, or
much harder, than it was actually.

so I think we should ask Felipe more about the unsolvable problems in PHP,
and maybe we shouldn't stop discussions about old topics, because maybe the
environment around the problems changed with time.

Tyrael

--0016364d27a5b2689c04940c4fee--