Re: Memory leak in flex generated file

John Millaway <johnmillaway@yahoo.com>
27 Oct 2005 23:26:45 -0400

          From comp.compilers

Related articles
Memory leak in flex generated file pavel.orehov@gmail.com (pavel.orehov@gmail.com) (2005-10-20)
Re: Memory leak in flex generated file haberg@math.su.se (2005-10-23)
Re: Memory leak in flex generated file gneuner2@comcast.net (George Neuner) (2005-10-23)
Re: Memory leak in flex generated file johnmillaway@yahoo.com (John Millaway) (2005-10-26)
Re: Memory leak in flex generated file Markus.Elfring@web.de (2005-10-26)
Re: Memory leak in flex generated file haberg@math.su.se (2005-10-27)
Re: Memory leak in flex generated file haberg@math.su.se (2005-10-27)
Re: Memory leak in flex generated file johnmillaway@yahoo.com (John Millaway) (2005-10-27)
Re: Memory leak in flex generated file johnmillaway@yahoo.com (John Millaway) (2005-10-29)
Memory leak in flex generated file pierreir@look.ca (Pierre Innocent) (2007-08-20)
Re: Memory leak in flex generated file jnvolkov@gmail.com (commander) (2007-08-21)
| List of all articles for this month |

From: John Millaway <johnmillaway@yahoo.com>
Newsgroups: comp.compilers
Date: 27 Oct 2005 23:26:45 -0400
Organization: Compilers Central
References: 05-10-161
Keywords: lex

> [This is a variant version of flex, not the one that is distributed
> with the GNU tools. They've made a lot of changes to it and I haven't
> looked at them in enough detail to know how much I like what they've
> done. -John]


It's been a while, but from the top of my head, here's what's new in Flex:


* Reentrant scanner.
* User-supplied memory management.
* Tables may be loaded/unloaded on the fly, from disk/network,etc.
* Generated C header file as well as C file.
* Bison integration (yylloc/yylval support).
* yylineno optimized.
* Numerous bug fixes.
* Regression test suite.
* texinfo manual.
* FAQ built from years of email Vern collected.


We took extreme pains and much of our time to please the unplacable, to
answer to the cries of incompatibility with DOS, pre-ANSI C, and OS's without
fork, as well as the dubious perspective that scanners and parsers should be
cleaved apart, ne'er to embrace one another. As such, the scanner skeleton is
mangled beyond recognition, so that it may be demangled by the likes of `m4`,
flex's preprocessor, and eventually the C preprocessor.


-Millaway


Post a followup to this message

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