|flex code memory usage firstname.lastname@example.org (=?ISO-8859-1?Q?Stefan_Fr=FChwirth?=) (2004-02-01)|
|Re: flex code memory usage email@example.com (=?ISO-8859-1?Q?Stefan_Fr=FChwirth?=) (2004-02-04)|
|Re: flex code memory usage ChrisIsbell_nospaam@voila.fr (Chris Isbell) (2004-02-04)|
|Re: flex code memory usage ChrisIsbell@voila.fr (Chris Isbell) (2004-02-08)|
|Date:||4 Feb 2004 21:47:52 -0500|
|Posted-Date:||04 Feb 2004 21:47:52 EST|
> Using flex for a embedded system :O. I don't think it's a better idea. Is
> your embedded product that complex? What does your chip support ?
It's a IP2022 from Ubicom
(http://www.ubicom.com/products/ip2000/ip2000.html). And maybe it's
not correct to call it a embedded system...
> Hand written lexer/parser will be a better idea.
Maybe, but are there any solutions that are less complex than flex?
Some form of lexer generator, but not that complex. Maybe you know
something like this.
> If you do not clear memory will the product be fool proof? Will there be
> side effects?
I maybe shouldn't do this task, it may be a little bit too complicated
for me, but I think, when a call of yylex is finished, the heap used
by it is not freed. That's my problem, but maybe I've seen something
[You might take a look at re2c, recently mentioned here. -John]
Return to the
Search the comp.compilers archives again.