On 05/17/2011 09:58 AM, Ferenc Kovacs wrote:
On Tue, May 17, 2011 at 6:49 PM, Stas Malyshev<smalys...@sugarcrm.com>wrote:
Hi!
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.
on the sidenote, I don't think that many people out there would start
debuging the php src if they are presented with an error by the engine.
but I'm fine with Andi's suggestion.
While that is true, I did run across some code a while back that used
the tokenizer extension in conjunction with the error messages. If we
decouple the error messages completely from the tokens there would be no
way to write that same code. An edge case, but I don't think it hurts to
keep the token name there.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
