Re: flex scanner too huge, suggestions?

Tim Josling <tej@melbpc.org.au>
23 Feb 2001 00:00:29 -0500

          From comp.compilers
Related articles
flex scanner too huge, suggestions? troy@bell-labs.com (Troy Cauble) (2001-02-17)
Re: flex scanner too huge, suggestions? tej@melbpc.org.au (Tim Josling) (2001-02-23)
Re: flex scanner too huge, suggestions? snicol@apk.net (Scott Nicol) (2001-02-23)
Re: flex scanner too huge, suggestions? rkrayhawk@aol.com (2001-02-23)
Re: flex scanner too huge, suggestions? olsenc@ichips.intel.com (2001-02-25)
Re: flex scanner too huge, suggestions? Ron@Profit-Master.com (Ron Pinkas) (2001-02-25)
Re: flex scanner too huge, suggestions? troy@bell-labs.com (Troy Cauble) (2001-03-01)
| List of all articles for this month |
From: Tim Josling <tej@melbpc.org.au>
Newsgroups: comp.compilers
Date: 23 Feb 2001 00:00:29 -0500
Organization: Melbourne PC User Group
References: 01-02-097
Keywords: lex
Posted-Date: 23 Feb 2001 00:00:29 EST

One possibility that is often used is 'keywords'. If there is a
large class of tokens that match a generic pattern, you can have
the scanner match the pattern, then look up which one it is in a
keyword table. Most 3GL compilers do this.


Flex also has various table compression options eg -Cm (compress
and use meta equivalence classes). See the manual.


Tim Josling


Troy Cauble wrote:


> I have a working flex/bison implementation to parse a text
> protocol. The problem is that the scanner is huge.

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.