Re: $obj->attr::method() is not allowed
| From: | Laruence | Date: | Mon, 03 Sep 2012 16:17:44 +0000 |
| Subject: | Re: $obj->attr::method() is not allowed | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-62753@lists.php.net to get a copy of this message | ||
On Tue, Sep 4, 2012 at 12:05 AM, Andrew Faulds <ajf@ajf.me> wrote:
> 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 :(
if you don't, you will get a complex executor.
>
>>> 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
I really don't get it, you are saying current is bad, but every
language has defects, either parser, or executor.
why do you think rewrite a new parser will make every think perfect?
there is no perfect language at all.
thanks
>
> --
> Andrew Faulds
> http://ajf.me/
>
--
Laruence Xinchen Hui
http://www.laruence.com/