Related articles |
---|
Looking for Unix lex for modern systems arnold@skeeve.com (2022-01-06) |
Re: Looking for Unix lex for modern systems gah4@u.washington.edu (gah4) (2022-01-06) |
Re: Looking for Unix lex for modern systems gah4@u.washington.edu (gah4) (2022-01-07) |
Re: Looking for Unix lex for modern systems gah4@u.washington.edu (gah4) (2022-01-07) |
Re: Looking for Unix lex for modern systems arnold@skeeve.com (2022-01-09) |
Re: Looking for Unix lex for modern systems gah4@u.washington.edu (gah4) (2022-01-09) |
Re: Looking for Unix lex for modern systems gah4@u.washington.edu (gah4) (2022-01-12) |
From: | arnold@skeeve.com (Aharon Robbins) |
Newsgroups: | comp.compilers |
Date: | Sun, 9 Jan 2022 19:04:34 -0000 (UTC) |
Organization: | Aioe.org NNTP Server |
References: | 22-01-023 22-01-025 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="28948"; mail-complaints-to="abuse@iecc.com" |
Keywords: | lex, history |
Posted-Date: | 09 Jan 2022 16:45:07 EST |
In article 22-01-025, gah4 <gah4@u.washington.edu> wrote:
>On Thursday, January 6, 2022 at 4:09:53 PM UTC-8, Aharon Robbins wrote:
>> Can anyone point me at a version of Unix lex that will run on Linux?
>
>A web search for lex source found this:
>
>http://heirloom.sourceforge.net/devtools.html
>
>which sounds like exactly what you want.
I got this to build and run, but it ran out of buffer space. :-(
I have since made good progress with flex. The original lexer
was doing its own token buffering. I moved to using yytext, and
also changed YY_INPUT to get one character of input at a time
as lex used to do. These two together have allowed me to make
real progress.
Performance isn't an issue, so doing one character at a time is fine.
Thanks everyone for the help.
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
Return to the
comp.compilers page.
Search the
comp.compilers archives again.