Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52441
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.21 cause and error)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: internals@lists.php.net
References: <BANLkTimOZPjAu_mJSctXPL3x41QUekFtkw@mail.gmail.com>
 <BANLkTimUN1fqfZGai6cYG7sK=HHYFh72fw@mail.gmail.com>
 <887FE7CFF6F8DE4BB3A9535F53AFD06A492D09D2@il-ex2.zend.net>
 <4DD2A731.9000400@sugarcrm.com>
Date: Wed, 18 May 2011 09:42:07 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?=
 =?utf-8?Q?ca_do_I=2ES=2ET=2E?=
Message-ID: <op.vvn44ha0idpuyk@clk-0081.clk-domain>
In-Reply-To: <4DD2A731.9000400@sugarcrm.com>
User-Agent: Opera Mail/11.10 (Win32)
Subject: Re: [PHP-DEV] Re: [RFC] Improved parser error message
From: glopes@nebm.ist.utl.pt ("Gustavo Lopes")

Em Tue, 17 May 2011 17:49:53 +0100, Stas Malyshev <smalyshev@sugarcrm.com>  
escreveu:

> I think we need to keep token name in the message, since it makes it  
> easier to understand what parser expected if you need to debug the  
> parser (as opposed to your code). So I think we need to have both the  
> human-readable name and the token name, as Andi suggested.

I think this alternative has very little value for debugging the parser.  
There are no repeated labels for the tokens, so even if you don't know the  
token name by heart, you can look it up in 10 seconds.

Keeping the token name will only perpetuate the confusion it has caused. I  
think it ought to be dropped, but if no consensus can be reached, this  
would be better than the status quo.

-- 
Gustavo Lopes