Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50094 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20302 invoked from network); 3 Nov 2010 21:21:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Nov 2010 21:21:37 -0000 X-Host-Fingerprint: 95.31.13.88 xdmitri2.static.corbina.ru Received: from [95.31.13.88] ([95.31.13.88:13380] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/00-20176-F52D1DC4 for ; Wed, 03 Nov 2010 16:21:36 -0500 Message-ID: To: internals@lists.php.net References: <20101101123058.GL6051@celeron.flupzor.nl> <20101101123624.GC528@croustillant.local> Date: Thu, 4 Nov 2010 00:21:33 +0300 Lines: 16 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-RFC2646: Format=Flowed; Original X-Posted-By: 95.31.13.88 Subject: Re: [PHP-DEV] [alexander.schrijver@gmail.com: Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON] From: dmda@yandex.ru ("jvlad") > > Yes, there is a reason: > > As it was explained before, lemon would not display token names but > actual token "values". So instead of "Unexpected T_PAABLAH" it would say > "Unexpected '::' ..." > hello, value of some tokens is not what would be expected either. Think a bit about T_STRING for example. There should be a smart algorithm implemented. BTW bison-createdparsercan use a callback (yytnamerr) to replace tokens with something human-readable. Why not use it?