|Writing an interpreter Arne.Evertsson@Octalogic.se (1996-06-01)|
|Re: Writing an interpreter email@example.com (Psi) (1996-06-08)|
|Re: Writing an interpreter firstname.lastname@example.org (1996-06-08)|
|Re: Writing an interpreter email@example.com (1996-06-13)|
|Re: Writing an interpreter firstname.lastname@example.org (1996-06-13)|
|From:||email@example.com (Arne Dag Fidjestoel)|
|Date:||13 Jun 1996 17:55:16 -0400|
|Organization:||Norwegian University of Science and Technology|
firstname.lastname@example.org (Lambert Lum) writes:
>You played with flex/lex, right? It's got some great functionality for
>scanning text. Yeah, you guessed it. I'm embedding an interpreter into flex.
>Flex's text scanning by regular expressions is really cool. I just set
>the regular expressions to pick up what I want, and then for every
>regular expression, I got a pre-defined behavior in response. Simple, heh?
have you considered re2c?
the regexp stuff is a bit weaker than flex, but the neat thing is that
it gives you full control on the input stream ( you has to provide
routines for it ). re2c takes a specification resembling flex and
generates hardcoded-c to recognize input.
email@example.com < arne dag fidjestoel >
Return to the
Search the comp.compilers archives again.