Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:22311
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Fri, 10 Mar 2006 00:15:14 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <794761398.20060310001514@marcus-boerger.de>
To: Sara Golemon <pollita@php.net>
Cc: internals@lists.php.net
In-Reply-To: <009701c643a1$2809bbc0$7d051fac@stumpy>
References: <7.0.1.0.2.20060309124054.06c31238@zend.com> <dup2a5$h3e$1@sea.gmane.org> <004701c6439b$8d6cd6b0$7d051fac@stumpy> <dupnc8$9c2$1@sea.gmane.org> <009701c643a1$2809bbc0$7d051fac@stumpy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Give the Language a Rest motion
From: helly@php.net (Marcus Boerger)

Hello Sara,

  but if we were moving from flex to re2c for that tokenizing scripts we'd
get a nice speed boost, too. Typically re2c based scanners are 2 to 3 times
faster than lex based ones. And oh-re2c allows unicode scanning (2 byte
input) and you can use the same .re to generate two .c files if necessary.

best regards
matcus

Thursday, March 9, 2006, 6:44:45 PM, you wrote:

>>> The inability to inject tokens and expressions into the lexer and
>>> parser is another limitation on what can be done from extensions in
>>> terms of syntax level features.  Yes, I know this is more of a problem
>>> with bison and flex than with the design of ZE, but that doesn't make
>>> it any less bothersome.
>>
>> Do other compiler tools allow this?
>>
> I've heard second hand that lemon does.  But I'm quite certain that 
> rewriting the lexer/parser is not at the top of the list of productive ways 
> to advance the language.

> -Sara 




Best regards,
 Marcus