Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52438 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57576 invoked from network); 17 May 2011 16:58:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 May 2011 16:58:21 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.215.170 mail-ey0-f170.google.com Received: from [209.85.215.170] ([209.85.215.170:56712] helo=mail-ey0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/E0-53005-B29A2DD4 for ; Tue, 17 May 2011 12:58:20 -0400 Received: by eyf5 with SMTP id 5so207866eyf.29 for ; Tue, 17 May 2011 09:58:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=VmHFWVjVe941yJWGx9PdQGTejGSBZOOrW2Xp0DMxLQs=; b=IC+Z0AHFofc9X5xIurUlbX6r1re0GRp24o/3F+jnqv3O+u8mKfRGbFKuBkkZ0mH0lt p4CDubLZJmIhDTKy/h9KZVDhhJT/Iy9RXr44elS9ynWD2DM+hCaBnxHDagXJBs2ZBy5K o95i/RiQY8QlbOdxLujmZ5tk6vU9yXbCdtOKo= 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=cCdoHxLHxlW9fd6wI/lambXZjcuOXBRPwIrWJvwLhTs+QCv/L6JLN1wYeoIG0ro+4j ZJRqKjabjJXvjEq1NiBnOKSlaNZpyWPdmmQMcclXaGRt6ITxNuSHQvCEw3IbSDXT/aK4 OWIZxaIsEuThCiIQPA5fJfiEDKwhJHDJjmSn4= MIME-Version: 1.0 Received: by 10.14.97.2 with SMTP id s2mr277956eef.52.1305651496897; Tue, 17 May 2011 09:58:16 -0700 (PDT) Sender: tyra3l@gmail.com Received: by 10.14.37.13 with HTTP; Tue, 17 May 2011 09:58:16 -0700 (PDT) In-Reply-To: <4DD2A731.9000400@sugarcrm.com> References: <887FE7CFF6F8DE4BB3A9535F53AFD06A492D09D2@il-ex2.zend.net> <4DD2A731.9000400@sugarcrm.com> Date: Tue, 17 May 2011 18:58:16 +0200 X-Google-Sender-Auth: y5GYpwLGwmWudd8pkDFaEd0L12Y Message-ID: To: Stas Malyshev Cc: internals Content-Type: multipart/alternative; boundary=bcaec52be78dac4c3604a37bad6f Subject: Re: [PHP-DEV] Re: [RFC] Improved parser error message From: info@tyrael.hu (Ferenc Kovacs) --bcaec52be78dac4c3604a37bad6f Content-Type: text/plain; charset=UTF-8 On Tue, May 17, 2011 at 6:49 PM, Stas Malyshev 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. Tyrael --bcaec52be78dac4c3604a37bad6f--