home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!darwin.sura.net!mips!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!cherokee!copper!mcain
- From: mcain@copper (Michael Cain)
- Subject: Re: yacc and lex
- Message-ID: <1992Jul22.135605.12853@advtech.uswest.com>
- Sender: news@advtech.uswest.com (Radio Free Boulder)
- Nntp-Posting-Host: copper.advtech.uswest.com
- Organization: U S WEST Advanced Technologies
- References: <1992Jul21.164738.1@mcclb0.med.nyu.edu> <WEILER.92Jul21213719@crabapple.cis.ohio-state.edu>
- Date: Wed, 22 Jul 1992 13:56:05 GMT
- Lines: 23
-
- In article <WEILER.92Jul21213719@crabapple.cis.ohio-state.edu> weiler@crabapple.cis.ohio-state.edu (Jerry Weiler) writes:
- >In article <1992Jul21.164738.1@mcclb0.med.nyu.edu> ramirez@mcclb0.med.nyu.edu writes:
- >
- >> I would like to know if anybody has ported yacc and lex
- >> over to linux. If yes, please let me know where I can find it.
- >
- >You should use bison and flex. bison is the GNU replacement for yacc
- >and flex is the GNU replacement for lex. They're faster, more flexible
- >and all around better. Bison and flex should be able to handle any
- >grammer yacc and lex do (any well written one, that is)
-
- Flex does have one significant handicap when compared to lex: in lex,
- the default i/o functions are actually macros, which can be #undef'ed
- and replaced with real functions of the same name that can get input
- from anywhere; flex has real functions that insist on reading from
- files, and trying to replace these is semi-major surgery...
-
- I regularly seem to want to parse stuff and don't want to let the
- analyzer built by flex handle my low-level file i/o...
-
- Mike Cain
- U S WEST Advanced Technologies
- mcain@advtech.uswest.com
-