Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62752 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95450 invoked from network); 3 Sep 2012 16:06:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Sep 2012 16:06:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 64.22.89.133 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 64.22.89.133 oxmail.registrar-servers.com Received: from [64.22.89.133] ([64.22.89.133:45480] helo=oxmail.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A4/FE-20751-575D4405 for ; Mon, 03 Sep 2012 12:06:14 -0400 Received: from [192.168.0.200] (5ad3285b.bb.sky.com [90.211.40.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id E28017580CD; Mon, 3 Sep 2012 12:06:09 -0400 (EDT) Message-ID: <5044D54E.9090008@ajf.me> Date: Mon, 03 Sep 2012 17:05:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: Laruence CC: ivan.enderlin@hoa-project.net, internals@lists.php.net References: <5044C3E6.8040202@hoa-project.net> <5044CA5C.9080208@ajf.me> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] $obj->attr::method() is not allowed From: ajf@ajf.me (Andrew Faulds) On 03/09/12 17:03, Laruence wrote: > It is great parser(simple and fast) which make php works well for years.. No, it's not, it's overly complex. You have to define all sorts of different expression and variable variations :( >> rewrite the parser for what? for more academism? No, because current one is constraining implementation of some things, and making some things impossible. (we are limited, for instance, in options for order that generator expressions (e.g. Python's [i*2 for i in range(6)]) could be) >> we will rewrite it soon or later, but it's not because current one is >> bad, it will because a better parser tool shows up... Well, current one is bad. It only works well for some common cases. For others, it doesn.t -- Andrew Faulds http://ajf.me/