|justify use of flex vs. lex - summary email@example.com (1993-02-01)|
|Re: justify use of flex vs. lex - summary firstname.lastname@example.org (1993-02-04)|
|From:||email@example.com (Steve Layten x3451)|
|Date:||Mon, 1 Feb 1993 21:17:30 GMT|
I need to use flex instead of lex for a job I have that exceeds
capacities of some lex features. I want to put this into a
"production" job stream, and our current "standards" seem to
discourage use of public-domain code in production, the standard
managment argument being that we should use vendor-supported code
so we don't have to spend time maintaing the code ourselves. I
must justify the use of this "non-supported" code in production.
I would appreciate hearing comments from this community regarding
arguments for or against the use of flex vs. the vendor-supplied lex.
Some additional considerations which I think are important are:
[reasons deleted ]
Several persons, including the moderator indicated that flex contained
fewer bugs or had better support than lex: (firstname.lastname@example.org (Ken Yap),
email@example.com, firstname.lastname@example.org (Zalman Stern),
email@example.com (Randy Wright),
firstname.lastname@example.org (Anton Ertl)).
One or two specifically mentioned performance:
(email@example.com (Scott David Daniels),
firstname.lastname@example.org (Randy Wright)).
Others indicated that I should consider paying others for support. Cygnus
Support (contact: email@example.com (Don Rector), 415/903-1408) was mentioned
by three persons: (firstname.lastname@example.org (Craig Burley),
email@example.com (Joe Buck), (also gave
firstname.lastname@example.org as e-mail address)
email@example.com (Joe Korty)).
Randy Wright (firstname.lastname@example.org) also pointed out some additional
features of flex:
>For example, I needed a re-entrant scanner to interpret ansi terminal
>codes into curses calls. It took an afternoon to modify flex to run
>in a re-entrant fashion.
>Flex has the exclusive start conditions that lex (at least my
>version) lacks. I have found the exclusive start condition feature
>very useful in state machine tasks.
Finally one person (Basile STARYNKEVITCH <email@example.com>)
suggested that I look at PCCTS:
"It is a lexical+syntaxical analyser generator having more
features than yacc+lex and their derivatives (flex, bison). PCCTS
is public domain, (not GPL copylefted) so you can use it for
commercial products without violating its notice, which explicitly
permit use for commerical or proprietary software (both prohibited
by bison&flex's copyright)."
He include a README file (fairly long, which I will not include), and
indicated that PCCTS files are available via anon ftp from
marvin.ecn.purdue.edu (128.46.179) in the subdirectory pub/pccts/1.06
(beginning December 1, 1992).
Thank-you all for your help,
Steven W. Layten, Senior Engineer
Chemical Abstracts Service, PO Box 3012, Columbus, OH 43210 +1 614 447 3600
INET: firstname.lastname@example.org BITNET: swl26@cas UUCP: osu-cis!chemabs!swl26
Return to the
Search the comp.compilers archives again.