Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62857 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3172 invoked from network); 6 Sep 2012 09:26:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Sep 2012 09:26:04 -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 67.192.241.153 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.153 smtp153.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.153] ([67.192.241.153:33150] helo=smtp153.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/00-03079-A2C68405 for ; Thu, 06 Sep 2012 05:26:04 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp25.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id A1E0A2D059E; Thu, 6 Sep 2012 05:26:00 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp25.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 58DDB2D0319; Thu, 6 Sep 2012 05:26:00 -0400 (EDT) Message-ID: <50486C27.20200@sugarcrm.com> Date: Thu, 06 Sep 2012 02:25:59 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: "Morgan L. Owens" CC: PHP internals References: <50474A30.1090802@nznet.gen.nz> <5047D4A6.9030003@sugarcrm.com> <50486327.9050606@nznet.gen.nz> In-Reply-To: <50486327.9050606@nznet.gen.nz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: Moving to an AST-based parsing/compilation process From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Well, apart from perhaps leaving them with a simpler language that > doesn't have the inconsistencies and corner cases that currently exist > (and documented ad nauseum) not because of any design decision but > "because the parser is written that way". If you think writing new parser gets rid of all corner cases you are in for a big surprise. AST is not magic and parser will always be written exactly the way it is written - so if somebody won't implement certain feature in a consistent way, it won't be implemented in consistent way, AST or not. And it's a bit late to take design decisions on existing PHP language, it seems to me. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227