Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53448 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95032 invoked from network); 20 Jun 2011 20:27:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jun 2011 20:27:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.163 smtp163.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.163] ([207.97.245.163:48735] helo=smtp163.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 81/51-22948-31DAFFD4 for ; Mon, 20 Jun 2011 16:27:00 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp56.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 450B53D82F1; Mon, 20 Jun 2011 16:26:57 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp56.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 8A4813D8334; Mon, 20 Jun 2011 16:26:56 -0400 (EDT) Message-ID: <4DFFAD0F.4090608@sugarcrm.com> Date: Mon, 20 Jun 2011 13:26:55 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Christopher Jones CC: "internals@lists.php.net" References: <4DFA7EDF.5050802@sugarcrm.com> <4DFF9F94.4010306@oracle.com> In-Reply-To: <4DFF9F94.4010306@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] 5.4 features for vote (long) From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! On 6/20/11 12:29 PM, Christopher Jones wrote: > If messages are changing, can we feasibly strip the Bison "syntax > error, " component? The "Command line code" component is arguably > useless too. Or at least it could be lower cased to "command line", > though changing this in php_cli.c may have an unwanted cascading > effect (?) I would assume "Command line code" comes from filename component of the metadata for the code being parsed. I guess it would be possible to detect when it's command-line and skip it, but what for? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227